https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100446
--- Comment #15 from R. Diez <rdiez-2006 at rd10 dot de> --- I just tested -g3 with a bigger, non-LTO firmware, and I am not seeing excessive CPU load and memory usage with GDB anymore. Debugging seems right. The versions are: cross-compiler GCC 15.2, Binutils 2.45 and GDB 16.3. So I guess this bug can be closed now. Like I said, when I turn LTO on, then GDB cannot find any C preprocessor macros anymore, but that is probably the different GDB bug we have mentioned. With LTO and -O2 optimisation, GDB uses much more memory, and does a couple of short pauses when hitting a breakpoint or stepping through. I guess it is loading much more debugging information than with non-LTO, -O0 builds. But both memory and CPU load are not excessive anymore.
