From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 61F7C3841452; Sat,  4 Jun 2022 17:46:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 61F7C3841452
From: "rajpal.gusain at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29188] gdb too slow and hogs memory for debug binary
 generated with gcc 11.2
Date: Sat, 04 Jun 2022 17:46:09 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 11.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: rajpal.gusain at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29188-4717-3plFgIz1CV@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29188-4717@http.sourceware.org/bugzilla/>
References: <bug-29188-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jun 2022 17:46:09 -0000

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

--- 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 sh=
are
few observations

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

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

% readelf --debug-dump=3Dmacro gold-g | grep 'import.*0x0$' | wc -l=20
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.=20
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 breakpoin=
t 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 o=
ther
issues with it as I mentioned before) ?

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



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

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