public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug corefiles/31506] New: [gdb/corefiles, aarch64] FAIL: gdb.base/corefile2.exp: renamed binfile: print/x buf_rw[0]@4
@ 2024-03-18 10:27 vries at gcc dot gnu.org
2024-03-26 7:22 ` [Bug corefiles/31506] " vries at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2024-03-18 10:27 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-03-26 7:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-18 10:27 [Bug corefiles/31506] New: [gdb/corefiles, aarch64] FAIL: gdb.base/corefile2.exp: renamed binfile: print/x buf_rw[0]@4 vries at gcc dot gnu.org
2024-03-26 7:22 ` [Bug corefiles/31506] " vries at gcc dot gnu.org
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).