public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30103] New: GDB gets confused about what is the current source file for various actions
Date: Thu, 09 Feb 2023 16:31:09 +0000 [thread overview]
Message-ID: <bug-30103-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30103
Bug ID: 30103
Summary: GDB gets confused about what is the current source
file for various actions
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: luis.machado at arm dot com
CC: vries at gcc dot gnu.org
Target Milestone: ---
Host: aarch64-linux
Target: aarch64-linux
Build: aarch64-linux
As described in here, gdb seems to get confused about what is the current
source file to use for commands like break / list / info source.
In particular, there seems to be a manifestation of this confusion when the
source file is the same and doesn't have any directory components to it.
Attached is an example of how the test fails on aarch64-linux Ubuntu 22.04. It
doesn't fail for aarch64-linux Ubuntu 20.04 though.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-02-09 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 16:31 luis.machado at arm dot com [this message]
2023-02-09 16:32 ` [Bug gdb/30103] " luis.machado at arm dot com
2023-02-10 11:07 ` [Bug testsuite/30103] " vries at gcc dot gnu.org
2023-02-10 14:58 ` cvs-commit at gcc dot gnu.org
2023-02-10 14:59 ` 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-30103-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).