-
Notifications
You must be signed in to change notification settings - Fork 150
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
Look into how mingw produces DWARF-in-PE #40
Comments
@jon-turney has submitted patches to Breakpad to support this use case, maybe he can point us at some resources that explain what mingw does. |
Specifically, there's this patchset that adds support for dumping symbol information from mingw PE files: https://codereview.chromium.org/1451693003/ |
I'm not sure there's much to explain. The same DWARF information sections are present, but the container is PECOFF rather than ELF. |
DWARF sections names in PE files are stored indirectly through a symbol table. Names of the form "/n" where "n" is a number indicate the section name is stored in index "n" of a hidden symbol table. The hidden symbol table immediately follows the COFF symbol table and is a sequence of null terminated CStrings.
DWARF sections names in PE files are stored indirectly through a symbol table. Names of the form "/n" where "n" is a number indicate the section name is stored in index "n" of a hidden symbol table. The hidden symbol table immediately follows the COFF symbol table and is a sequence of null terminated CStrings.
Fixed in #69 |
DWARF sections names in PE files are stored indirectly through a symbol table. Names of the form "/n" where "n" is a number indicate the section name is stored in index "n" of a hidden symbol table. The hidden symbol table immediately follows the COFF symbol table and is a sequence of null terminated CStrings.
Issue gimli-rs#40 -- Support DWARF-in-PE
The mingw toolchain produces PE binaries with DWARF in them. I'm not 100% sure how it works, but it should be possible to support with gimli+object. This is a follow-on from #39 .
The text was updated successfully, but these errors were encountered: