public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31290] New: gdb.base/list-nodebug.exp failure
Date: Wed, 24 Jan 2024 16:17:43 +0000 [thread overview]
Message-ID: <bug-31290-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31290
Bug ID: 31290
Summary: gdb.base/list-nodebug.exp failure
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: simark at simark dot ca
Target Milestone: ---
On Debian 12, I see:
(gdb) run
Starting program:
/home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/list-nodebug/list-nodebug
warning: amd-dbgapi: unable to enable GPU debugging due to a restriction error
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 1, 0x000055555555512d in main ()
(gdb) list .
No symbol table is loaded. Use the "file" command.
(gdb) FAIL: gdb.base/list-nodebug.exp: first 'list .'
list .
No symbol table is loaded. Use the "file" command.
(gdb) FAIL: gdb.base/list-nodebug.exp: second 'list .'
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-01-24 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 16:17 simark at simark dot ca [this message]
2024-01-24 16:18 ` [Bug gdb/31290] " simark at simark dot ca
2024-03-16 23:06 ` vries at gcc dot gnu.org
2024-03-17 9:17 ` vries at gcc dot gnu.org
2024-03-17 9:17 ` [Bug testsuite/31290] " vries at gcc dot gnu.org
2024-03-17 9:32 ` vries at gcc dot gnu.org
2024-03-17 15:47 ` cvs-commit at gcc dot gnu.org
2024-03-17 15:48 ` 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-31290-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).