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 corefiles/31506] New: [gdb/corefiles, aarch64] FAIL: gdb.base/corefile2.exp: renamed binfile: print/x buf_rw[0]@4
Date: Mon, 18 Mar 2024 10:27:56 +0000 [thread overview]
Message-ID: <bug-31506-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31506
Bug ID: 31506
Summary: [gdb/corefiles, aarch64] FAIL: gdb.base/corefile2.exp:
renamed binfile: print/x buf_rw[0]@4
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: corefiles
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On aarch64-linux (debian 12), I run into:
...
(gdb) file
/home/linux/gdb/build/gdb/testsuite/outputs/gdb.base/corefile2/corefile2^M
Reading symbols from
/home/linux/gdb/build/gdb/testsuite/outputs/gdb.base/corefile2/corefile2...^M
(gdb) print/x buf_rw[0]@4^M
Cannot access memory at address 0x60090^M
(gdb) FAIL: gdb.base/corefile2.exp: renamed binfile: print/x buf_rw[0]@4
...
At first glance, this looks like a relocation issue:
...
(gdb) p &buf_rw[0]
$1 = 0x60090 <buf_rw> ""
(gdb) start
...
(gdb) p &buf_rw[0]
$2 = 0xaaaaaab00090 <buf_rw> ""
....
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-03-18 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 10:27 vries at gcc dot gnu.org [this message]
2024-03-26 7:22 ` [Bug corefiles/31506] " 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-31506-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).