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

["me at dominicclifton dot name" <sourceware-bugzilla@sourceware.org>]

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

Dominic Clifton <me at dominicclifton dot name> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |me at dominicclifton dot name

--- Comment #7 from Dominic Clifton <me at dominicclifton dot name> ---
I would like to add this this is NOT fixed, see GDB traces below:

```
516,275 ~"Reading symbols from
D:\\Users\\Hydra\\Documents\\dev\\projects\\betaflight\\betaflight\\o\
bj\\main\\betaflight_STM32H725_CHONKERH735.elf...\n"
516,333 39-list-thread-groups i1
548,419
~"/data/jenkins/workspace/GNU-toolchain/arm-12-mpacbti/src/binutils-gdb--gdb/gdb/utils.c:717\
: internal-error: virtual memory exhausted: can't allocate 4064 bytes.\nA
problem internal to GDB ha\
s been detected,\nfurther debugging may prove unreliable."
```

12.2.MPACBTI-Rel1

I also confirm that using '-ggdb' vs '-ggdb3' is a working temporary workaround
for me.

When '-ggdb3' is used the GDB sessions takes forever to start and the debugger
will crash.

I also note that I do not experience crashing issues using 9.3.1 of GCC (GNU
Arms Tools release), but every version of GDB since that has the issue.

Here's the list of ones I've tried.

```
 Volume in drive D is NVME1_DATA1
 Volume Serial Number is 0641-FCA8

 Directory of D:\Programs\GNUArmTools

17/07/2023  21:18    <DIR>          .
17/07/2023  21:18    <DIR>          ..
17/07/2023  21:18    <JUNCTION>     active
[D:\Programs\GNUArmTools\gcc-arm-none-eabi-9-2020-q2-update-win32]
27/10/2022  16:58    <DIR>         
arm-gnu-toolchain-11.3.rel1-mingw-w64-i686-arm-none-eabi
14/03/2023  09:36    <DIR>         
arm-gnu-toolchain-12.2.mpacbti-rel1-mingw-w64-i686-arm-none-eabi
12/12/2022  19:28    <DIR>         
arm-gnu-toolchain-12.2.rel1-mingw-w64-i686-arm-none-eabi
27/07/2021  10:25    <DIR>          gcc-arm-none-eabi-10.3-2021.07
20/09/2021  11:35    <DIR>          gcc-arm-none-eabi-6-2017-q1-update-win32
20/09/2021  11:35    <DIR>          gcc-arm-none-eabi-6-2017-q2-update-win32
20/09/2021  11:34    <DIR>          gcc-arm-none-eabi-6_2-2016q4-20161216-win32
20/09/2021  11:35    <DIR>          gcc-arm-none-eabi-7-2017-q4-major-win32
20/09/2021  11:36    <DIR>          gcc-arm-none-eabi-7-2018-q2-update-win32
20/09/2021  11:36    <DIR>          gcc-arm-none-eabi-8-2018-q4-major-win32
20/09/2021  11:36    <DIR>          gcc-arm-none-eabi-8-2019-q3-update-win32
20/09/2021  11:37    <DIR>          gcc-arm-none-eabi-9-2019-q4-major-win32
20/09/2021  11:32    <DIR>          gcc-arm-none-eabi-9-2020-q2-update-win32
               6 File(s)            525 bytes
              16 Dir(s)  55,371,231,232 bytes free
```

Please can this be re-opened, triaged and fixed?  Happy to provide more
information as required.

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