Skip to content
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

Open
lastmjs opened this issue Jan 17, 2024 · 5 comments
Open

Error stack traces #126

lastmjs opened this issue Jan 17, 2024 · 5 comments

Comments

@lastmjs
Copy link

lastmjs commented Jan 17, 2024

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.

@lastmjs
Copy link
Author

lastmjs commented Jan 25, 2024

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

@subbu963
Copy link
Contributor

@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.
did you guys find any solution?

@L-jasmine
Copy link
Collaborator

@subbu963 Can you provide me with a reproducible example?

@subbu963
Copy link
Contributor

@L-jasmine try running this javascript snippet. It wont throw any error.

console.log(someNonExistingVariable.a)

@subbu963
Copy link
Contributor

subbu963 commented May 3, 2024

@L-jasmine did you get a chance to check the above?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants