From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ADFAB3858413; Wed, 19 Jul 2023 13:48:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ADFAB3858413 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689774504; bh=cnUB8UwWMocQGfeg44kCAwn38MQ19okw5BZr9/wWak0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HvyVO/tmebQgpC4RkTz7JRhc1XNOVf+hYko6YGZdKUuORzWg5AviTBCbDzlNhp38N Cpk3kSVNnJb0mq7r8l9tiLp0Ty95Nsxtxo09n4s3GxZnQTwsOAyBt/qJu9v3l0aQyC DBdiKnd6LyokYbyisvxgav3jVt1vXGxX/Itoaj8c= From: "luis.machado at arm dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: luis.machado at arm dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D28219 --- Comment #16 from Luis Machado --- Thanks for the additional information. I would've expected the 12.2-Rel1 to= ols 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. Meanwh= ile, can you do debugging with no macro information? Simon, do you know if anything has been done with regards to these macro im= port issues? --=20 You are receiving this mail because: You are on the CC list for the bug.=