[Bug gdb/29188] gdb too slow and hogs memory for debug binary generated with gcc 11.2

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29188

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #12 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to gusain from comment #11)

> With gold, I have 0 occurrences but binary is no good because when I bring
> it up in gdb, source information seems to be incorrect. When I put a
> breakpoint in my code, gdb tells me that it's in some libstdc++ file.

This sounds like a different problem, which we'd have to investigate
separately.

> Do you still think it's not gdb bug ? If not, whose bug is it ?

I think the mold author put in a workaround for this issue.
While pedantically it may be a gcc bug, in practice the fixes are in the
linker.

> Are you aware of any workaround (gold link doesn't work for me and I have
> other issues with it as I mentioned before) ?

GNU ld should work, or an updated mold.  I'm unsure about lld.

> Do you think it's gold linker bug and I should file a ticket for it ? Is
> there information I can get which can shed more light on this gold-linked
> binary issue  ? 

I'm afraid I don't know the answer here.

Since I think this particular bug is another instance of the macro-import
problem, I'm closing it as a dup.

*** This bug has been marked as a duplicate of bug 27754 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.