search

second-state / wasmedge-quickjs

A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge.
Apache License 2.0
494 stars 60 forks source link

Error stack traces #126

Open lastmjs opened 9 months ago

lastmjs commented 9 months ago

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 commented 8 months ago

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 commented 5 months ago

@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 commented 5 months ago

@subbu963 Can you provide me with a reproducible example?

subbu963 commented 5 months ago

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

console.log(someNonExistingVariable.a)
subbu963 commented 5 months ago

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