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 tdep/30506] New: [gdb/tdep, aarch64] FAIL: gdb.dwarf2/dw2-prologue-end-2.exp: $break_addr == $foo_label_addr
Date: Thu, 01 Jun 2023 12:15:08 +0000 [thread overview]
Message-ID: <bug-30506-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30506
Bug ID: 30506
Summary: [gdb/tdep, aarch64] FAIL:
gdb.dwarf2/dw2-prologue-end-2.exp: $break_addr ==
$foo_label_addr
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE Leap 15.4 aarch64 I run into:
...
(gdb) break foo^M
Breakpoint 1 at 0x4005f8: file
/home/tdevries/gdb/src/gdb/testsuite/gdb.dwarf2/dw2-prologue-end-2.c, line
26.^M
(gdb) PASS: gdb.dwarf2/dw2-prologue-end-2.exp: break foo
print /x &foo_label^M
$1 = 0x4005f0^M
(gdb) PASS: gdb.dwarf2/dw2-prologue-end-2.exp: print /x &foo_label
print &foo_end == &bar_label^M
$2 = 1^M
(gdb) PASS: gdb.dwarf2/dw2-prologue-end-2.exp: print &foo_end == &bar_label
FAIL: gdb.dwarf2/dw2-prologue-end-2.exp: $break_addr == $foo_label_addr
...
This was noted here (
https://sourceware.org/pipermail/gdb-patches/2023-April/199053.html ).
This WIP ( https://sourceware.org/pipermail/gdb-patches/2023-April/199056.html
) fixes the FAIL on aarch64.
Also on arm, as mentioned here (
https://sourceware.org/pipermail/gdb-patches/2023-May/199614.html ).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-06-01 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 12:15 vries at gcc dot gnu.org [this message]
2023-06-01 12:18 ` [Bug tdep/30506] " vries at gcc dot gnu.org
2023-06-02 5:36 ` luis.machado at arm dot com
2023-06-07 8:39 ` luis.machado at arm dot com
2023-06-07 11:01 ` cvs-commit at gcc dot gnu.org
2023-06-07 11:02 ` luis.machado at arm dot com
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-30506-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).