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

["rajpal.gusain at gmail dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #11 from gusain <rajpal.gusain at gmail dot com> ---
Thanks for your help. It does seem like it's similar to 27754 but let me share
few observations

% readelf --debug-dump=macro ld-g | grep 'import.*0x0$' | wc -l 
277652

% readelf --debug-dump=macro lld-g | grep 'import.*0x0$' | wc -l 
277655

% readelf --debug-dump=macro gold-g | grep 'import.*0x0$' | wc -l 
0

You had a comment on other ticket that it doesn't seem to affect lld but my
binary linked with ldd doesn't suggest it. 
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.


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

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

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  ? 



(In reply to Tom Tromey from comment #10)
> (In reply to gusain from comment #9)
> 
> > Is there any other information I can get to confirm it's same as other issue
> > you mentioned ?
> 
> Try something like:
> 
> readelf --debug-dump=macro | grep 'import.* 0x0$'
> 
> See bug #27754

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