public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "me at dominicclifton dot name" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28219] arm-none-eabi-gdb, .../gdb/utils.c:671: "internal-error: virtual memory exhausted: can't allocate 4064 bytes"
Date: Tue, 18 Jul 2023 16:10:15 +0000	[thread overview]
Message-ID: <bug-28219-4717-XiAserWiJc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28219-4717@http.sourceware.org/bugzilla/>

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

--- Comment #10 from Dominic Clifton <me at dominicclifton dot name> ---
Created attachment 14983
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14983&action=edit
requested .elf file that causes GDB to crash

```
arm-none-eabi-gcc.exe (Arm GNU Toolchain 12.2.MPACBTI-Rel1 (Build
arm-12-mpacbti.34)) 12.2.1 20230214
```

source for testing:

https://github.com/hydra/betaflight/commits/bf-stm32h725

Note there are two important commits in the branch:

168741486eac3dd0eb43efd40bc20c024ac50904 - changes the Makefile so that '-ggdb'
is used instead of `-ggdb3`
9407467d8be0cab4b492f30d6089f5e1bcd9cadc - parent commit of above used to build
the attached binaries.

Note that if you want to re-build the above binaries from the source you'll
need
```
GCC_REQUIRED_VERSION=12.2.1
```
in `mk\local.mk`, and then build with:

```
make CHONKERH735 DEBUG=INFO EXTRA_FLAGS="-DUSE_TIMER_MAP_PRINT"
```

Full GDB trace log also included in the `.zip` along with the corresponding
`.map` file

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

  parent reply	other threads:[~2023-07-18 16:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 20:32 [Bug gdb/28219] New: " bmcdonnell at fischerblock dot com
2021-08-10 20:33 ` [Bug gdb/28219] " bmcdonnell at fischerblock dot com
2022-04-22  9:12 ` jose.simoes at eclo dot solutions
2022-05-04 23:58 ` jose.simoes at eclo dot solutions
2022-05-05 13:44 ` simon.marchi at polymtl dot ca
2022-10-13  9:20 ` luis.machado at arm dot com
2022-10-21 10:00 ` luis.machado at arm dot com
2023-07-11 14:45 ` bmcdonnell at fischerblock dot com
2023-07-18 14:10 ` me at dominicclifton dot name
2023-07-18 14:32 ` luis.machado at arm dot com
2023-07-18 16:02 ` me at dominicclifton dot name
2023-07-18 16:10 ` me at dominicclifton dot name [this message]
2023-07-19  9:56 ` luis.machado at arm dot com
2023-07-19 12:01 ` me at dominicclifton dot name
2023-07-19 13:01 ` luis.machado at arm dot com
2023-07-19 13:04 ` luis.machado at arm dot com
2023-07-19 13:35 ` me at dominicclifton dot name
2023-07-19 13:48 ` luis.machado at arm dot com
2023-07-19 13:49 ` luis.machado at arm dot com
2023-07-19 14:07 ` me at dominicclifton dot name
2023-07-19 14:56 ` simon.marchi at polymtl dot ca
2023-07-19 16:12 ` luis.machado at arm dot com
2023-07-20  1:30 ` simon.marchi at polymtl dot ca
2023-07-20 13:45 ` luis.machado at arm dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-28219-4717-XiAserWiJc@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).