-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
geseparate_dwarf, symbol files, and external_debug_info reference #11516
Comments
Sounds reasonable to me, and the syntax sounds ok too. @dschuff what do you think? |
The idea seems reasonable to me too. So the idea is that the bit before the |
Yes, I think that's the suggestion. |
Another thing it might be worthwhile to support might be something like a GNU build ID, which uniquely identifies a build. That way the debugger can use whatever means it wants to locate the debug info, and the build ID can go into the external debug info section. |
(this was actually suggested in WebAssembly/tool-conventions#133) |
In `-gseparate-dwarf` mode the debug info is in a file on the side, while the main file has a URL to it. This allows customizing that URL so that the debug file can be hosted in a custom location relative to the main file. fixes #11516
Compiling with -geseparate_dwarf=foo.wasm currently has the effect of generating a foo.wasm file containing all DWARF data, and will also insert an external_debug_info custom section into the code module containing a string 'foo.wasm'.
It would be great to increase flexibility here. For instance, what if I want to point to the symbol module by absolute URL? I'd propose supporting a mapping syntax such as for --embed-file:
-gseparate_dwarf=./foo.wasm@http://.../foo.wasm
The text was updated successfully, but these errors were encountered: