-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught Exception #117
Comments
Hey, I had a quick stab at debugging. I made a bit of progress in https://github.com/ExpoSEJS/ExpoSE/tree/debugging but It looks like either some language feature or runtime override is conflicting both with our runtime overrides and Jalangi's, possibly something that the transpiler is doing. It looks like jalangi now crashes on a call to an undefined function sometime after entering the _possibleConstructorReturn function (I assume this is something that the transpiler has created). I'll try to take another look when I have some more time.
|
Thank you so much for looking into this! I'll also try to debug this further Ultimately, I want to extract the path conditions for each fully explored path. I noticed these crashes while testing the tool and reading the logs. I assume that these crashes are terminating those paths earlier. |
Hi 👋
Thanks for sharing this project!
I wanted to report the following exception. The exception is thrown here, despite it being surrounded by a try/catch. Unfortunately, I'm not yet able to tell why this was triggered.
In order for this to reach this point, I had to fix the following code:
How to reproduce:
npm install bignumber.js runtime-generator
EXPOSE_PRINT_PATHS=1 EXPOSE_LOG_LEVEL=3 expoSE ./repro.js
The text was updated successfully, but these errors were encountered: