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 3C46C394504E; Fri, 23 Apr 2021 20:31:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3C46C394504E
From: "rdiezmail-binutils at yahoo dot de" <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:31:37 +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: rdiezmail-binutils at yahoo dot de
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-MUNiGicxG5@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:31:38 -0000

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

--- Comment #4 from rdiezmail-binutils at yahoo dot de ---

> For me it also fails, but that's because this
> symbol isn't defined in the release ELF.

Yes, I'm sorry, with the release ELF you can try another symbol instead, li=
ke
this one:

(gdb) print BareMetalSupport_Reset_Handler
$1 =3D {void (void)} 0x86a98 <BareMetalSupport_Reset_Handler()>

That rises the GDB memory usage to a whopping 5,6 GiB.

In fact, I do not understand why StartOfUserCode is not defined in the rele=
ase
build, because it is the same source code after all. The same routine is us=
ed
in the same way.

I dumped all symbols like this and I compared them:

arm-none-eabi-objdump  --syms  firmware-debug-non-lto.elf
arm-none-eabi-objdump  --syms  firmware-release-lto.elf

The release ELF seems to have lost most C++ symbols, and there are many ent=
ries
like this:

00010d6b l       .debug_info    00000000=20
00010d6b l       .debug_info    00000000=20
00010d6b l       .debug_info    00000000=20
00010d6b l       .debug_info    00000000=20

With GCC's -g2 there is no memory problem anymore, but the C++ symbols are
still missing, and those weird entries above are still there.

It may be a compiler problem indeed. But I do not know enough about GCC's L=
TO
and GDB to tell. I am really only a user. For example, I do not know that a=
 CU
is.

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