From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 056D93858411; Tue, 21 Dec 2021 21:25:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 056D93858411 From: "rdiezmail-binutils at yahoo dot de" To: gdb-prs@sourceware.org Subject: [Bug macros/27754] Excessive CPU load and memory usage with -g3 debug info Date: Tue, 21 Dec 2021 21:25:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: macros 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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2021 21:25:10 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27754 --- Comment #18 from rdiezmail-binutils at yahoo dot de --- I just did another test after upgrading the toolchain to these versions: BINUTILS_VERSION :=3D 2.37 GMP_VERSION :=3D 6.2.1 MPFR_VERSION :=3D 4.1.0 MPC_VERSION :=3D 1.2.1 GCC_VERSION :=3D 10.3.0 NEWLIB_VERSION :=3D 4.1.0 GDB_VERSION :=3D 11.1 I rebuilt the JtagDue firmware, release LTO -g3, and checked in the build l= og that -g3 was actually being passed to GCC. Then I loaded the firmware with: "$HOME/rdiez/arduino/JtagDue/SelfTestOutput/CurrentToolchain/bin/arm-none-e= abi-gdb" "firmware-release-lto-g3.elf" The GDB commands I typed were: print BareMetalSupport_Reset_Handler info macro STACK_SIZE There was neither a delay nor a high memory consumption. But the #define ma= cros were not visible with GDB. Command "info macro" yields the following error message: The symbol `STACK_SIZE' has no definition as a C/C++ preprocessor macro I then built a debug build (without LTO) and the results were the same: no #define macros were visible with GDB. Am I doing something wrong? I cannot remember how I viewed C preprocessor macros inside GDB in the past. I checked, and macros are present in the debug information, as this command confirms: readelf --debug-dump "firmware-release-lto-g3.elf" | grep STACK_SIZE The output is: DW_MACRO_define_strp - lineno : 64 macro : STACK_SIZE ( 4 * 1024 ) I'll try to attach the ELF files after this comment. I cannot test with GDB 11.1 or 11.2 because of the cross-compilation toolch= ain build problem described in this bug comment: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98324#c7 --=20 You are receiving this mail because: You are on the CC list for the bug.=