public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "bmcdonnell at fischerblock dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28219] New: arm-none-eabi-gdb, .../gdb/utils.c:671: "internal-error: virtual memory exhausted: can't allocate 4064 bytes" Date: Tue, 10 Aug 2021 20:32:46 +0000 [thread overview] Message-ID: <bug-28219-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28219 Bug ID: 28219 Summary: arm-none-eabi-gdb, .../gdb/utils.c:671: "internal-error: virtual memory exhausted: can't allocate 4064 bytes" Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: bmcdonnell at fischerblock dot com Target Milestone: --- Created attachment 13613 --> https://sourceware.org/bugzilla/attachment.cgi?id=13613&action=edit gdb crash after breakpoint (VSCode) Using the latest GNU Arm Embedded Toolchain (10.3-2021.07) available from here: https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads With a Segger J-Link BASE, when I set a breakpoint, the breakpoint hits, but there is no way for me to control/resume program execution, and the debugger crashes - as shown in the attached screenshot. This issue does not occur with GNU Arm Embedded Toolchain 9-2020-q2-update. Other details of my environment: - Windows 10 version 21H1 (OS Build 19043.1110) - J-Link tools V7.52c (latest stable) - Visual Studio Code (VSCode) 1.59.0 (user setup), with Cortex-Debug plugin v0.3.13 Preview ---------- GDB error text from screenshot: /mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-260_20210727_1627371386/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. /mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-260_20210727_1627371386/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-08-10 20:32 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-10 20:32 bmcdonnell at fischerblock dot com [this message] 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 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@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: linkBe 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).