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 C1A313828912; Fri, 27 May 2022 12:50:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C1A313828912
From: "simark at simark dot ca" <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: Fri, 27 May 2022 12:50:58 +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: simark at simark dot ca
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-PF77DYYgTb@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: Fri, 27 May 2022 12:50:58 -0000

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

--- Comment #5 from Simon Marchi <simark at simark dot ca> ---
Well, your backtraces do show GDB reading macro information, so there's got=
ta
be some somewhere.

Actually, you can turn on:

(gdb) set debug dwarf-read 1

prior to running your experiment.  You should get some messages like this, =
that
will help you know which CU in which file GDB is slow at reading:

[dwarf-read] process_queue: Expanding one or more symtabs of objfile
/home/simark/build/binutils-gdb-one-target/gdb/gdb ...
[dwarf-read] process_queue: Expanding symtab of CU at offset 0x1054

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