-
Notifications
You must be signed in to change notification settings - Fork 7
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
source debugging of compiled wasm #18
Comments
It's already been working for a while for C / C++: https://developer.chrome.com/blog/wasm-debugging-2020/ As for other languages, it's up to respective toolchains to correctly emit debugging information. Rust support in particular - assuming you're talking about the Web via wasm-bindgen - is tracked on their own repo at rustwasm/wasm-bindgen#2389. |
@RReverser thx, the use case I have in mind is for non-web Rust, no wasm-bindgen, just FFI pointers, compiled with |
Then it's up to wasm3 to implement debugging, although knowing the author's situation (he's a Ukrainian who lost his home to Russian bombarding), I don't know if he'll have time / priority to work on it soon. Rust itself emits debug symbols correctly though, and some runtimes like wasmtime already make use of it: https://docs.wasmtime.dev/examples-debugging.html Either way, this is not really an issue / discussion for the standards repo, since it's up to specific runtimes to implement the necessary functionality now. |
okay, thanks a lot for your response, unfortunately I can't use wasmtime due to JIT compilation, so wasm3 is the only option. |
is there any support for debugging source code compiled to wasm in sight? (i.e. Rust code)
The text was updated successfully, but these errors were encountered: