public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31290] gdb.base/list-nodebug.exp failure Date: Sun, 17 Mar 2024 15:47:47 +0000 [thread overview] Message-ID: <bug-31290-4717-UZr2veAiw3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31290-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31290 --- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=42db3e48c5532a6a4aa3952e0a3d02f3dfac6f0a commit 42db3e48c5532a6a4aa3952e0a3d02f3dfac6f0a Author: Tom de Vries <tdevries@suse.de> Date: Sun Mar 17 16:48:43 2024 +0100 [gdb/testsuite] Fix gdb.base/list-no-debug.exp on debian On debian 12, aarch64-linux I run into: ... (gdb) list .^M No symbol table is loaded. Use the "file" command.^M (gdb) FAIL: gdb.base/list-nodebug.exp: first 'list .' ... The test-case expects some debug info, but none for main. Instead, there's no debug info at all. Fix this by adding another source file to the test-case, and compiling it with debug info. Tested on aarch64-linux. Approved-By: Andrew Burgess <aburgess@redhat.com> PR testsuite/31290 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31290 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-17 15:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-24 16:17 [Bug gdb/31290] New: " simark at simark dot ca 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 [this message] 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-UZr2veAiw3@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: linkBe 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).