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 1F9C539450F4; Fri, 23 Apr 2021 20:52:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F9C539450F4
From: "dblaikie at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27754] Excessive CPU load and memory usage with -g3 debug
 info
Date: Fri, 23 Apr 2021 20:52:08 +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: dblaikie at gmail dot com
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: 
Message-ID: <bug-27754-4717-dN4geyiJZy@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: Fri, 23 Apr 2021 20:52:09 -0000

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

--- Comment #5 from David Blaikie <dblaikie at gmail dot com> ---
>>From the email thread:

My high water mark reported my massif for the non-lto build was 197MB - mos=
t of
that seems to come from decoding the macro information (dwarf_decode_macros=
).=20
...
Oh, managed to get the lto case to stop & valgrind to log it.

Yeah... peaked out over 5GB of memory usage, and:
74.12% (4,372,282,848B) 0x3A4D42: macro_alloc

So it seems to be something in the way gdb is storing macro info (consistent
with the "-g2 rather than -g3 significantly reduces the memory usage" data)

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