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 gdb/31507] New: [gdb, aarch64] FAIL: gdb.arch/disp-step-insn-reloc.exp: can_relocate_adr_forward: relocated instruction
Date: Mon, 18 Mar 2024 12:32:12 +0000 [thread overview]
Message-ID: <bug-31507-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31507
Bug ID: 31507
Summary: [gdb, aarch64] FAIL:
gdb.arch/disp-step-insn-reloc.exp:
can_relocate_adr_forward: relocated instruction
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On aarch64-linux (debian 12) I ran into:
...
(gdb) PASS: gdb.arch/disp-step-insn-reloc.exp: can_relocate_adr_forward: go to
breakpoint 6
continue^M
Continuing.^M
^M
Breakpoint 8, can_relocate_adr_forward () at
/home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:356^M
356 asm ("set_point6:\n"^M
(gdb) FAIL: gdb.arch/disp-step-insn-reloc.exp: can_relocate_adr_forward:
relocated instruction
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-03-18 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 12:32 vries at gcc dot gnu.org [this message]
2024-03-18 14:03 ` [Bug gdb/31507] " vries at gcc dot gnu.org
2024-03-18 14:08 ` vries at gcc dot gnu.org
2024-03-18 14:08 ` vries at gcc dot gnu.org
2024-03-18 14:10 ` vries at gcc dot gnu.org
2024-03-18 14:55 ` vries at gcc dot gnu.org
2024-03-18 15:08 ` vries at gcc dot gnu.org
2024-03-18 15:11 ` [Bug tdep/31507] " vries at gcc dot gnu.org
2024-03-18 15:21 ` luis.machado at arm dot com
2024-03-18 15:21 ` luis.machado at arm dot com
2024-03-18 15:23 ` luis.machado at arm dot com
2024-03-18 17:20 ` luis.machado at arm dot com
2024-03-18 17:49 ` vries at gcc dot gnu.org
2024-03-18 18:05 ` luis.machado at arm dot com
2024-03-19 7:20 ` vries at gcc dot gnu.org
2024-03-19 8:13 ` luis.machado at arm dot com
2024-03-22 13:30 ` luis.machado at arm dot com
2024-05-06 12:09 ` 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-31507-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).