From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5B14838582A1; Wed, 19 Jul 2023 14:07:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5B14838582A1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689775649; bh=gNpXVXwm13NDXHoUvdw0udwx0/MH5MqBBBYqIfYWO6M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=K2p4672wTT1HjRIH48fZ4+S7wWUnTWAg+AHBgvCDFGgljXl6As7qAxbU1F1xIZN/p 4DGa+Py5sCJ4ADvWoeXoFhYu0gFSeXiCaAEFw7jSB/N5I743xnmMThxExmKYUlMVfA 4dZMrcInh0t14zZbGGNTeif63lkxGFNhLLBlQTr4= From: "me at dominicclifton dot name" 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 14:07:28 +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: me at dominicclifton dot name 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 #18 from Dominic Clifton --- Hi again Luis, > 2 - Build the elf without macro information. It may not work if you need = to debug macros. I have never needed this directly, and I'm not aware if my IDE (Eclipse, CL= ion, VSCode) requires this, I doubt it though since I can debug ok using '-ggdb' which according to the documentation uses the default level of '2' which do= es not contain the macro debugging information.=20 Using '-ggdb2' instead of '-ggdb3' may be a useful workaround for myself and others and is a good way to specify that macro debugging information is /no= t/ used, rather than relying on the default, which may change over time. Yes, please raise this on the mailing list again, with a priority given to option 3, making GDB workaround the issue, which is a solution that will not have to wait for a tools update and should provide immediate benefits. Yes, please add me to the CC list or ping me for the new issue when you cre= ate it. --=20 You are receiving this mail because: You are on the CC list for the bug.=