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 BF93138515FF; Thu,  6 May 2021 11:13:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BF93138515FF
From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27754] Excessive CPU load and memory usage with -g3 debug
 info
Date: Thu, 06 May 2021 11:13:44 +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: 10.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: cc
Message-ID: <bug-27754-4717-jm7Bh2fImi@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27754-4717@http.sourceware.org/bugzilla/>
References: <bug-27754-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: Thu, 06 May 2021 11:13:44 -0000

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note that .debug_macro is output at the GCC compile-stage, and thus
DW_AT_GNU_macro is only present in the "abstract" CUs.  That might lead
to multiple inclusions of macro sections in case gdb follows
DW_AT_abstract_origins from concrete CUs to the abstract ones (and in
case it doesn't employ any "caching" of already read macro sections ...)

.debug_macro of the LTO build is

  [15] .debug_macro      PROGBITS        00000000 153940 028492

while the non-LTO build shows

  [11] .debug_macro      PROGBITS        00000000 07a360 027965

that's almost the same size (as expected).  So the issue must be with
how gdb interprets this info.  The non-LTO .debug_macro has

 DW_MACRO_import - offset : 0x0
 DW_MACRO_end_file

as well, whatever that means.

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