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.

Sign up for GitHub

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

Jump to bottom

wasm-node: On panic, load a separate Wasm source map and resolve the backtrace #83

Closed
tomaka opened this issue Feb 9, 2023 · 1 comment
Closed

wasm-node: On panic, load a separate Wasm source map and resolve the backtrace #83

tomaka opened this issue Feb 9, 2023 · 1 comment
Labels
blocked Progress on this issue requires something beyond our control

Comments

@tomaka
Copy link
Contributor

tomaka commented Feb 9, 2023

paritytech/smoldot#1916
@tomaka tomaka added the blocked Progress on this issue requires something beyond our control label Feb 10, 2023
@tomaka tomaka changed the title wasmnode On panic load a separate Wasm source map and resolve the backtrace wasm-node: On panic, load a separate Wasm source map and resolve the backtrace Mar 29, 2023
@tomaka
Copy link
Contributor Author

tomaka commented Nov 25, 2023

Closing as "won't do".
In practice, backtraces are almost never useful when debugging panics. The panic message and location and logs are more than enough.
While having a backtrace wouldn't hurt, it would significantly complexify the JS code.

@tomaka tomaka closed this as not planned Won't fix, can't repro, duplicate, stale Nov 25, 2023
@tomaka tomaka mentioned this issue Jan 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Progress on this issue requires something beyond our control
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomaka