Haven't used debuggers or debugged a lot just yet, but I've had this question in my mind and I'd like to inspect some debugging information manually. Are there some kind of documentation or specification and are there a lot of information that is hidden in a an average "debuggable" binary?
May 13, 2022 What exact debugging information is added to the binary and how to parse it all? | ||||
---|---|---|---|---|
| ||||
May 13, 2022 Re: What exact debugging information is added to the binary and how to parse it all? | ||||
---|---|---|---|---|
| ||||
Posted in reply to BoQsc | On Friday, 13 May 2022 at 16:11:14 UTC, BoQsc wrote: >Haven't used debuggers or debugged a lot just yet, but I've had this question in my mind and I'd like to inspect some debugging information manually. Are there some kind of documentation or specification and are there a lot of information that is hidden in a an average "debuggable" binary? if you're on linux then the debug information are generated in a format that's well specified called DWARF. DWARF essentially contain information about
That's a lot of information, they non-trivially increase the size of the binary, but this is required to debug a program. learn more... |
Copyright © 1999-2021 by the D Language Foundation