[Bug macros/27754] Excessive CPU load and memory usage with -g3 debug info

["rdiezmail-binutils at yahoo dot de" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #18 from rdiezmail-binutils at yahoo dot de ---
I just did another test after upgrading the toolchain to these versions:

BINUTILS_VERSION := 2.37
GMP_VERSION := 6.2.1
MPFR_VERSION := 4.1.0
MPC_VERSION := 1.2.1
GCC_VERSION := 10.3.0
NEWLIB_VERSION := 4.1.0
GDB_VERSION := 11.1

I rebuilt the JtagDue firmware, release LTO -g3, and checked in the build log
that -g3 was actually being passed to GCC.

Then I loaded the firmware with:

"$HOME/rdiez/arduino/JtagDue/SelfTestOutput/CurrentToolchain/bin/arm-none-eabi-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 macros
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 toolchain
build problem described in this bug comment:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98324#c7

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