search for: debug_pubnames

Hi All, I just enabled the generation of dwarf debugging information for Hexagon. It did not require much save for the setting of a flag in MCAsmInfo. However, now I see that the ".debug_pubnames" sections is not generated. I did read discussion about the section not really being useful for debuggers in terms of accelerated access, but I have code that uses libdwarf to check for global variables. The particular libdwarf API queries the ".debug_pubnames" This code is no longer...

On Mar 8, 2012, at 2:29 PM, Pranav Bhandarkar wrote: > Hi All, > > I just enabled the generation of dwarf debugging information for Hexagon. It > did not require much save for the setting of a flag in MCAsmInfo. > > However, now I see that the ".debug_pubnames" sections is not generated. I > did read discussion about the section not really being useful for debuggers > in terms of accelerated access, but I have code that uses libdwarf to check > for global variables. The particular libdwarf API queries the > ".debug_pubnames" Th...

Hello all, I am implementing support for .debug_names section (which is introduced in DWARFv5 standard as replacement for .debug_pubnames and .debug_pubtypes). The question is: should usage of DWARF version 5 force generation of .debug_names instead of .debug_pubnames or we can make it just default behavior and provide user with the interface (cmd switch) to use other DWARFv5 features but generate old .debug_pubnames and .debug_...

...gt; Thanks for the information. After I sent out the email, I saw the patch you reverted on viewVC. I have some proprietary code that looks at the debug info in an executable using libdwarf; It queries the debug info on demand with a variable name and uses dwarf_get_globals which, I believe, uses .debug_pubnames. I believe you made only one change to take out support for this section, right ? I will revert that change and give it a go. Thanks, Pranav Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

...to have DWARF that has a class A that inherits from > class B, but only a forward declaration of class B is provided. Hmm do we emit that kind of thing today? In a naïve test, I'm seeing the full description of class B. > - LLDB wants the .apple_XXX accelerator tables, GDB wants > .debug_pubnames/.debug_pubtypes Agreed. > So it would be great to have a "-debugger" flag that could be specified > > -debugger=lldb > -debugger=gdb > > Not sure on the option name, but I do like the idea. We'll bikeshed the name later but yes, that's the plan. Thanks, --pa...

...d do:   - Remove obsolete debug info which refers to code deleted by the linker     doing the garbage collection (gc-sections).   - Deduplicate debug type definitions for reducing resulting size of binary.   - Build accelerator/index tables.     = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, .debug_pubtypes.   - Strip unneeded tables.     = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, .debug_pubtypes.   - Compress or decompress debug info as requested. Possible feature:   - Join split dwarf .dwo files in a single file containing all debug info     (convert spl...

...n was built with -fno-limit-debug-info, which isn't a > default setup on linux. I have tried measuring the sizes without that > flag and with fission enabled (-gsplit-dwarf) and the results are: > without compression: > - clang binary: 960 MB > - .debug_names: 130 MB (13%) > - debug_pubnames: 175 MB (18%) > - debug_pubtypes: 204 MB (21%) > - median time for setting a breakpoint on non-existent function > (variance +/- 2%): > real 0m3.526s > user 0m3.156s > sys 0m0.364s > > with -Wl,--compress-debug-sections=zlib: > - clang binary: 440 MB > - .debug_names:...

...ld be possible to fix this with a smarter implementation). >> >> As far as object file sizes go, in the resulting clang binary (2.3GB), >> the new .debug_names section takes up about 160MB (7%), which isn't >> negligible, but considering that it supersedes the >> .debug_pubnames/.debug_pubtypes tables whose combined size is 490MB >> (21% of the binary), switching to this table (and dropping the other >> two) will have a positive impact on the binary size. Further >> reductions can be made by merging the individual indexes into one >> large index as...

...ify -fno-limit-debug-info or some flag like that. I think the option is -f(no-)standalone-debug-info which only emits full definitions of classes in the object file that holds and object’s vtable. -- adrian > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants >>> .debug_pubnames/.debug_pubtypes >> >> Agreed. >> >>> So it would be great to have a "-debugger" flag that could be specified >>> >>> -debugger=lldb >>> -debugger=gdb >>> >>> Not sure on the option name, but I do like the idea. &g...

...> the linker >      doing the garbage collection (gc-sections). > >    - Deduplicate debug type definitions for reducing resulting > size of > binary. > >    - Build accelerator/index tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Strip unneeded tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Compress or decompress debug info as requested. > > Possible feature: > >    - Join split...

...> the linker >      doing the garbage collection (gc-sections). > >    - Deduplicate debug type definitions for reducing resulting > size of > binary. > >    - Build accelerator/index tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Strip unneeded tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Compress or decompress debug info as requested. > > Possible feature: > >    - Join split...

...other optimizations weren’t really helpful, so they were removed. > > which only emits full definitions of classes in the object file that holds and object’s vtable. > > -- adrian > > > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants > >>> .debug_pubnames/.debug_pubtypes > >> > >> Agreed. > >> > >>> So it would be great to have a "-debugger" flag that could be specified > >>> > >>> -debugger=lldb > >>> -debugger=gdb > >>> > >>> Not sure on th...

...ator mentioned above. That's something that GDB insists on having. (It turns out that the standard operator was defined in DWARF 3, so we also have to emit the GNU operator if we're producing DWARF 2. Tuning considerations don't trump what the standard says.) Another example would be .debug_pubnames and .debug_pubtypes sections. Currently these default to omitted for Darwin and PS4, but included everywhere else. My initial patch for "tuning" changes the PS4 platform criterion to the SCE debugger predicate; quite likely the "not Darwin" criterion ought to be "not LLDB&q...

...gc-sections). >> >>    - Deduplicate debug type definitions for reducing >> resulting size of >> binary. >> >>    - Build accelerator/index tables. >>      = .debug_aranges, .debug_names, .gdb_index, >> .debug_pubnames, >> .debug_pubtypes. >> >>    - Strip unneeded tables. >>      = .debug_aranges, .debug_names, .gdb_index, >> .debug_pubnames, >> .debug_pubtypes. >> >>    - Compress or decompress debug info as requeste...

...hat fake this by putting the section VMA at 0, the PE format will not allow it. */ /* DWARF 1.1 and DWARF 2. */ .debug_aranges BLOCK(__section_alignment__) (NOLOAD) : { *(.debug_aranges) } .zdebug_aranges BLOCK(__section_alignment__) (NOLOAD) : { *(.zdebug_aranges) } .debug_pubnames BLOCK(__section_alignment__) (NOLOAD) : { *(.debug_pubnames) } .zdebug_pubnames BLOCK(__section_alignment__) (NOLOAD) : { *(.zdebug_pubnames) } .debug_pubtypes BLOCK(__section_alignment__) (NOLOAD) : { *(.debug_pubtypes) } .zdebug_pubtypes BLOCK(__section_alignment__)...

...only does (2), perhaps it does some other things that we don't do, but I haven't seen it) which only emits full definitions of classes in the object file that holds and object’s vtable. -- adrian > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants >>> .debug_pubnames/.debug_pubtypes >> >> Agreed. >> >>> So it would be great to have a "-debugger" flag that could be specified >>> >>> -debugger=lldb >>> -debugger=gdb >>> >>> Not sure on the option name, but I do like the idea. >&g...

Another example would be .debug_pubnames and .debug_pubtypes sections. Currently these default to omitted for Darwin and PS4, but included everywhere else. My initial patch for "tuning" changes the PS4 platform criterion to the SCE debugger predicate; quite likely the "not Darwin" criterion ought to be "not LLDB&q...

...Deduplicate debug type definitions for reducing >>> resulting size of >>> binary. >>> >>>    - Build accelerator/index tables. >>>      = .debug_aranges, .debug_names, .gdb_index, >>> .debug_pubnames, >>> .debug_pubtypes. >>> >>>    - Strip unneeded tables. >>>      = .debug_aranges, .debug_names, .gdb_index, >>> .debug_pubnames, >>> .debug_pubtypes. >>> >>>...

..., the PE format will not allow it. */ > /* DWARF 1.1 and DWARF 2. */ > .debug_aranges BLOCK(__section_alignment__) (NOLOAD) : > { > *(.debug_aranges) > } > .zdebug_aranges BLOCK(__section_alignment__) (NOLOAD) : > { > *(.zdebug_aranges) > } > .debug_pubnames BLOCK(__section_alignment__) (NOLOAD) : > { > *(.debug_pubnames) > } > .zdebug_pubnames BLOCK(__section_alignment__) (NOLOAD) : > { > *(.zdebug_pubnames) > } > .debug_pubtypes BLOCK(__section_alignment__) (NOLOAD) : > { > *(.debug_pubtypes) &g...

...0. */ - /* DWARF 1 */ - .debug 0 : { *(.debug) } - .line 0 : { *(.line) } - /* GNU DWARF 1 extensions */ - .debug_srcinfo 0 : { *(.debug_srcinfo) } - .debug_sfnames 0 : { *(.debug_sfnames) } - /* DWARF 1.1 and DWARF 2 */ - .debug_aranges 0 : { *(.debug_aranges) } - .debug_pubnames 0 : { *(.debug_pubnames) } - /* DWARF 2 */ - .debug_info 0 : { *(.debug_info .gnu.linkonce.wi.*) } - .debug_abbrev 0 : { *(.debug_abbrev) } - .debug_line 0 : { *(.debug_line) } - .debug_frame 0 : { *(.debug_frame) } - .debug_str 0 : { *(.debug_str) } - .debug_loc 0 : {...