I have been given a tiny object file created by armcc using DWARF and things make no sense to me so far.
dwarfdump (and libdwarf) use the SHT_GROUP section data to associate sections to their group. This is a .o, not a fully linked executable or shared-library. (libdwarf assigns group numbers itself. group 1 is non-dwo .debug sections) (any .dwo sections present would be shown as group 2 if not listed in a section-group header, but no such are present here) Here is dwarfdump/libdwarf/s reading of the sections and section-group sections. Section Groups data Number of Elf-like sections: 35 Number of groups : 5 Group to print : 3 Count of map entries : 15 [index] group section [ 0] 1 4 .debug_frame [ 1] 1 5 .debug_info [ 2] 1 6 .debug_info [ 3] 1 7 .debug_line [ 4] 1 8 .debug_line [ 5] 1 9 .debug_loc [ 6] 1 10 .debug_macinfo [ 7] 1 11 .debug_pubnames [ 8] 3 13 .debug_info [ 9] 3 14 .debug_line [ 10] 4 16 .debug_info [ 11] 5 18 .debug_info [ 12] 5 19 .debug_line [ 13] 5 20 .debug_macinfo [ 14] 6 22 .debug_abbrev There are two .debug_info not in any group (called group 1 by libdwarf). There is only one .debug_abbrev and it is in group six. How is one to make sense of this? Which .debug_line (sec 7 or 8)would be referred to from section 6 debug_line? How would one know? Why is .debug_abbrev in a group by itself? I would appreciate any information on how the sections tie together... how is a reader supposed to know what goes with what? Thanks for any hints. David Anderson -- Duct tape is like the force. It has a light side, a dark side, and it holds the universe together.... -- Carl Zwanzig _______________________________________________ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
