-
Notifications
You must be signed in to change notification settings - Fork 61
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
Error stack traces #126
Comments
Not being able to see global unhandled errors in and outside of promises seems a major problem for me, I can't always tell what's going on, but this seems like a major setback for debugging |
@L-jasmine @lastmjs even i am facing the same problem. something breaks in js code but it doesnt tell me what or which line is the error at. |
@subbu963 Can you provide me with a reproducible example? |
@L-jasmine try running this javascript snippet. It wont throw any error. console.log(someNonExistingVariable.a) |
@L-jasmine did you get a chance to check the above? |
When using QuickJS through Javy JS exceptions provided the error message with a stack trace to the file and line number, which was very very useful.
Does wasmedge-quickjs have this capability? How can we get this functionality?
Lack of error messages with stack traces could be a major setback.
The text was updated successfully, but these errors were encountered: