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 632863856DCA; Tue, 25 Oct 2022 16:16:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 632863856DCA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1666714584;
	bh=AHl8tb32FHpUZQ2N7p8BqbF45XJrUaPE5wAm7XX8TLY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=EwUYG198IoJQvgCa81N9V9tK97mKBXZ64L7FsP4wRajAyh/L0d0u6UnFLkkzu0gTt
	 8b76hLzsMpXTuYhxhRLSkNuhnP79V45GX6cf1dWvWpJn6NI3SjEkrL9NaFy3e2zwXd
	 XApxM1RynVRssu86bj53E9MOMmrE2nBNerYR3q/4=
From: "tromey at sourceware dot org" <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: Tue, 25 Oct 2022 16:16:23 +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: tromey at sourceware dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-29188-4717-bKupGhVskl@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
List-Id: <gdb-prs.sourceware.org>

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

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  ?=20

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 ***

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