public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/26362] New: gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 187647121162241 bytes
Date: Mon, 10 Aug 2020 14:17:55 +0000 [thread overview]
Message-ID: <bug-26362-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26362
Bug ID: 26362
Summary: gdb/utils.c:671: internal-error: virtual memory
exhausted: can't allocate 187647121162241 bytes
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE tumbleweed:
...
(gdb) PASS: gdb.fortran/mixed-lang-stack.exp: lang=auto: set language auto
bt^M
#0 breakpt () at
/home/abuild/rpmbuild/BUILD/gdb-10.0.50.20200806/gdb/testsuite/gdb.fortran/mixed-lang-stack.f90:37^M
#1 0x0000aaaaaaaab5d8 in mixed_func_1h () at
/home/abuild/rpmbuild/BUILD/gdb-10.0.50.20200806/gdb/testsuite/gdb.fortran/mixed-lang-stack.f90:115^M
#2 0x0000aaaaaaaaafd8 in mixed_func_1g (obj=...) at
/home/abuild/rpmbuild/BUILD/gdb-10.0.50.20200806/gdb/testsuite/gdb.fortran/mixed-lang-stack.cpp:77^M
#3 0x0000aaaaaaaab020 in mixed_func_1f () at
/home/abuild/rpmbuild/BUILD/gdb-10.0.50.20200806/gdb/testsuite/gdb.fortran/mixed-lang-stack.cpp:84^M
#4 0x0000aaaaaaaaafbc in mixed_func_1e () at
/home/abuild/rpmbuild/BUILD/gdb-10.0.50.20200806/gdb/testsuite/gdb.fortran/mixed-lang-stack.cpp:67^M
#5 0x0000aaaaaaaab5bc in mixed_func_1d (a=1, b=2, c=3, d=(4,5),
str=../../gdb/utils.c:671: internal-error: virtual memory exhausted: can't
allocate 187647121162241 bytes.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
FAIL: gdb.fortran/mixed-lang-stack.exp: lang=auto: bt (GDB internal error)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-08-10 14:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:17 vries at gcc dot gnu.org [this message]
2020-08-10 14:18 ` [Bug tdep/26362] " vries at gcc dot gnu.org
2020-08-10 14:18 ` vries at gcc dot gnu.org
2020-08-10 14:26 ` [Bug tdep/26362] [aarch64] " vries at gcc dot gnu.org
2020-08-10 14:30 ` alahay01 at gcc dot gnu.org
2020-08-11 13:29 ` luis.machado at linaro dot org
2020-08-11 15:25 ` vries at gcc dot gnu.org
2020-08-11 19:38 ` luis.machado at linaro dot org
2020-08-12 7:50 ` vries at gcc dot gnu.org
2020-08-12 9:10 ` vries at gcc dot gnu.org
2020-08-12 12:19 ` vries at gcc dot gnu.org
2020-08-12 12:21 ` vries at gcc dot gnu.org
2020-08-12 12:31 ` vries at gcc dot gnu.org
2020-08-12 13:47 ` luis.machado at linaro dot org
2020-08-12 13:53 ` luis.machado at linaro dot org
2020-08-12 14:17 ` luis.machado at linaro dot org
2020-08-12 14:17 ` luis.machado at linaro dot org
2020-08-12 16:34 ` luis.machado at linaro dot org
2020-08-12 17:02 ` andrew.burgess at embecosm dot com
2020-08-12 17:17 ` luis.machado at linaro dot org
2020-08-12 17:23 ` vries at gcc dot gnu.org
2020-08-12 17:26 ` luis.machado at linaro dot org
2020-08-12 18:12 ` vries at gcc dot gnu.org
2020-08-12 18:20 ` luis.machado at linaro dot org
2020-08-12 18:32 ` luis.machado at linaro dot org
2020-08-12 19:06 ` luis.machado at linaro dot org
2020-08-12 21:13 ` vries at gcc dot gnu.org
2020-08-12 21:15 ` luis.machado at linaro dot org
2020-08-12 22:03 ` vries at gcc dot gnu.org
2020-08-12 22:19 ` luis.machado at linaro dot org
2020-08-14 15:46 ` vries at gcc dot gnu.org
2020-08-15 10:01 ` vries at gcc dot gnu.org
2020-08-15 10:05 ` vries at gcc dot gnu.org
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-26362-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: link
Be 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).