-
Notifications
You must be signed in to change notification settings - Fork 478
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
RuntimeError: abort(Error: <Insert my error here>). Build with -s ASSERTIONS=1 for more info. #493
Comments
Referring to the example demonstration of the bug... You can see this if you remove my
You'll notice that the I wonder if solc actually is generating the AST and then carrying on to make a binary, and the latter is the hidden process?That is after all what you'd expect a 'compile' command to do normally (i.e. not stop at AST creation). Although I don't use that output, perhaps the process still runs? Is there a way to stop that background process? |
I tried the newest v0.7.4 version of solc, and added the new Indeed, if (in the example demonstration), I increase the sleep time to 30 seconds and then throw an error, solc still wraps my errors. |
Thank you for reporting this! This sounds like a problem with the compilation to webassembly. |
Maybe related to #34 |
Did you find solution? |
For me, I also tend to run into these problems regularly and the problem is that before, in node.js, it seems something is dumping loads of data into my shell. Can this at least be prevented somehow? It makes debugging any earlier code quite tricky... Screen.Recording.2022-04-20.at.18.01.22.mov |
Hi @iAmMichaelConnor, @yilmazbingo, and @TimDaub, I looked at this problem, and apparently, it was fixed on version I.e. adding the following to your code (you can test it with your demo): const listeners = process.listeners("unhandledRejection");
process.removeListener("unhandledRejection", listeners[listeners.length - 1]); |
Hi!
EDIT: I've created a repo with a minimal example of the bug, for people to try out and confirm: https://github.com/iAmMichaelConnor/solc-error-demo
solc version: 0.7.1 (& tested with 0.7.4)
node version: 12.18.2 (& tested with latest lts v15.0.1)
I'm writing a node.js application which imports solc-js in one
.mjs
file to compile a solidity file and output the AST.During development, whenever my application breaks and throws an error, the console spits out a solc-related error. Strangely, the solc-related error will throw even for code that isn't using solc. It appears the file
./node_modules/solc/soljson.js
is somehow 'wrapping' my error messages.A consequence of this is that every time my application throws an error, the console is filled with the thousands of lines of code contained in the file
./node_modules/solc/soljson.js
.Below is an example console output upon my app erroring. (Notice that the actual error is unrelated to solc; I'm accidentally
push
ing toundefined
elsewhere in my app. In fact, at this stage of my app's code, solc has been long finished with, and will not be called upon again).Any ideas to stop solc wrapping errors?
Many thanks!
The text was updated successfully, but these errors were encountered: