info:c_memory_structure
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
info:c_memory_structure [2012/10/15 15:10] – [The missing piece: .debug_section] moritz | info:c_memory_structure [2012/10/16 15:23] (current) – [Using the debug info dump] moritz | ||
---|---|---|---|
Line 99: | Line 99: | ||
Here is the output on my machine: | Here is the output on my machine: | ||
- | < | + | < |
- | + | ||
- | struct: | + | |
Contents of the .debug_info section: | Contents of the .debug_info section: | ||
Line 243: | Line 241: | ||
This is a lot of output. Let's explain the different parts. | This is a lot of output. Let's explain the different parts. | ||
+ | |||
+ | Each line represents either the start of a new entity or adds an attribute to one. All entities and attributes have a unique address, encoded in hex. Each entity has a type, which determines the attributes it has. The entity line consists of a nesting level, the unique address followed by the entity' | ||
+ | |||
+ | ==== Finding the size information ==== | ||
+ | |||
Fist, it tells us what format the file has. In this case it is a '' | Fist, it tells us what format the file has. In this case it is a '' | ||
Line 259: | Line 262: | ||
Here, '' | Here, '' | ||
- | ==== Using the debug info dump ==== | ||
- | |||
- | The output of the debug info dump can be read again by a program in order to extract the '' | ||
==== Problems ==== | ==== Problems ==== |
info/c_memory_structure.1350313817.txt.gz · Last modified: 2012/10/15 15:10 by moritz