[llvm-bugs] [Bug 42030] lld doesn't generate DW_MACRO_import like ld.bfd does, leading to gdb cpu/memory hog

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Jun 30 23:04:00 PDT 2019


Fangrui Song <i at maskray.me> changed:

           What    |Removed                     |Added
                 CC|                            |i at maskray.me
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #1 from Fangrui Song <i at maskray.me> ---
% readelf --debug-dump=macro exe.bfd | grep 'DW_MACRO_import .* : 0x0' | wc -l
% readelf --debug-dump=macro exe.lld | grep 'DW_MACRO_import .* : 0x0' | wc -l

gcc -g3 or -ggdb3 generates .debug_macro sections.

  # I think gcc/dwarf2out.c optimize_macinfo_range is responsible for the
  .section      .debug_macro,"", at progbits
  .byte 0x7               # DW_MACRO_import
  .long .Ldebug_macro57   # relocation to a section symbol that may be in a
discarded comdat

.debug_macro,"G", at progbits,wm4.stl_tree.h.59.e99bfd6fdb0e5d5124d05bd97b997689,comdat

.Ldebug_macro105 is defined in .debug_macro which is in a comdat group called
Other object files may define sections in the same comdat group. When these
files are linked together, only the first comdat group is kept and the rest are

.debug_macro,"", at progbits is not in a comdat group so the question is how to
resolve .long .Ldebug_macro57

According to
http://www.sco.com/developers/gabi/latest/ch4.sheader.html#section_groups ,
such relocations to .Ldebug_macro should not be allowed.

> A symbol table entry with STB_LOCAL binding that is defined relative to one of a group's sections, and that is contained in a symbol table section that is not part of the group, must be discarded if the group members are discarded. References to this symbol table entry from outside the group are not allowed.

I think ld.bfd/gold/lld error if the section containing the relocation is
SHF_ALLOC. .debug* do not have the SHF_ALLOC flag and those relocations are

lld resolves such relocations to 0. ld.bfd and gold, however, have some
CB_PRETEND/PRETEND logic to resolve relocations to the definitions in the
prevailing comdat groups. The code is hacky and may not suit lld.

I think the proper fix of this problem is to patch gdb to ignore 0

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190701/75821af4/attachment.html>

More information about the llvm-bugs mailing list