public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <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, 19 Jul 2023 13:48:23 +0000 [thread overview] Message-ID: <bug-28219-4717-uD3GNtUd6J@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 #16 from Luis Machado <luis.machado at arm dot com> --- Thanks for the additional information. I would've expected the 12.2-Rel1 tools to contain patches to improve this situation on ld's side. A see a few ways to improve this situation: 1 - Tools update, which may take a little while. Old tools will still be broken. 2 - Build the elf without macro information. It may not work if you need to debug macros. 3 - Teach gdb how to workaround these pathological cases for now (seems simpler). 4 - Longer term, try to improve memory use for these expansions. It may be a harder problem to deal with, so it could take some time. I can raise this issue again on the gdb mailing list for discussion. Meanwhile, can you do debugging with no macro information? Simon, do you know if anything has been done with regards to these macro import issues? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-19 13:48 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 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 [this message] 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-uD3GNtUd6J@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).