From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 325FC3857C52; Fri, 14 Aug 2020 15:46:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 325FC3857C52
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/26362] [aarch64] gdb/utils.c:671: internal-error: virtual
 memory exhausted: can't allocate 187647121162241 bytes
Date: Fri, 14 Aug 2020 15:46:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: tdep
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
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: <bug-26362-4717-3M0EleLCjN@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26362-4717@http.sourceware.org/bugzilla/>
References: <bug-26362-4717@http.sourceware.org/bugzilla/>
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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2020 15:46:55 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D26362

--- Comment #26 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Luis Machado from comment #25)
> Interesting and sneaky.
>=20
> You should be aware that my fix to the malloc sanity check makes the test
> pass now, even though it attempts to allocate the large number of bytes a=
nd
> errors out.
>=20
> It just doesn't throw an internal error like before.

I think I've analyzed that bit here: PR26390 -
"gdb.fortran/mixed-lang-stack.exp: error reading variable in backtrace".

If we consider the scope of this PR the internal-error, I think we are done
here.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=