[Bug gdb/28219] arm-none-eabi-gdb, .../gdb/utils.c:671: "internal-error: virtual memory exhausted: can't allocate 4064 bytes"

["luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #11 from Luis Machado <luis.machado at arm dot com> ---
Hi Dominic,

Thanks for sharing the data. I gave this a try on Linux, and I can't reproduce
it with any of master, 12.1-Rel1 or 11.3-Rel1 gdb's. I did notice newer gdb's
take longer to load data, and that is most likely due to a rewrite in the DWARF
reader that cause some slowdowns in some situations.

Now, I've noticed you are using the windows version of the Arm toolchain. In
that case, the gdb binary will be a 32-bit executable.

During reading of symbols and debug info, expansions (specially with macro
info) may cause gdb to go over the limit of 4GB. While that is not an issue for
a 64-bit process, it likely is for a 32-bit process.

I think that is a limitation of the Windows toolchain release at the moment
(shipping 32-bit binaries). I'd advise getting in touch through the Arm
community forum and checking when 64-bit tools for Windows will be available.

Otherwise, I think using -g as opposed to -g3 might be another workaround for
now, unfortunately.

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