public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jose.simoes at eclo dot solutions" <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: Wed, 04 May 2022 23:58:02 +0000 [thread overview]
Message-ID: <bug-28219-4717-2WdQ4HW4d6@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 #2 from José Simões <jose.simoes at eclo dot solutions> ---
Here's some extra information about this: I'm compiling with -Og and originally
with -ggdb3.
With this I could set the option to stop at `main()` but continuing to the next
line was incredibly slow. Resuming execution works but, on hitting pause
button, the gbd overflow exception would pop and the debug would be terminated.
After changing the build options to -ggdb (or just -g) the debug started to
work again. Stops at main(). Moving to the next line occurs swiftly. Resuming
execution works as expected. And I can now pause and continue execution as many
times as I want.
Tested this with gdb from GCC 8-2019-q3-update and the latest 11.2-2022.02.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-04 23:58 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 [this message]
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
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-2WdQ4HW4d6@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).