-
Notifications
You must be signed in to change notification settings - Fork 68
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
Document debugging sections #148
Comments
Good idea. I'm actually not sure how much of this is temporary and how much is intended to be long term. (Or should we document things regardless, and update later?) cc @pfaffe |
I think at the very least we could start a document with In general, if something is around for a while, I think it's better to document it regardless, since there is already a set of tools that rely on a shared representation that is just undocumented otherwise. If it becomes obsolete, we can always mark it as such later down the road. |
I opened #149 now with info about DWARF and I did not add docs for |
Well it's supported in several browsers and toolchains (e.g. it's currently the only option for AssemblyScript - I think adding DWARF there will require quite a bit more effort and time), so I think it's still useful to document.
Sure, happy to add myself. |
@kripken As a next step, we'd probably need to document |
@RReverser Wouldn't that duplicate section 1.1 in @yurydelendik 's document? We link to there already. |
Hmm that's true, although same could be said about |
I'm not opposed, if you see value in it. |
Ouch, I accidentally committed from the Github UI instead of creating a PR: faf8131#diff-7ab4dad0c749e83db84252b8efa31ce713135e4329e4f4772b93f21ca7b2c081 |
@RReverser post-commit lgtm |
Several toolchains have supported
sourceMappingURL
custom section for years to encode source map URLs. Also nowadays Emscripten usesexternal_debug_info
custom section to encode URL of the external DWARF info.The Wasm debugging story is still in flux, but perhaps we should start documenting at least the custom sections and conventions already used in the wild, so that other tools can understand and parse those. cc @kripken @dschuff
The text was updated successfully, but these errors were encountered: