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] [gdb, aarch64] FAIL: gdb.arch/disp-step-insn-reloc.exp: can_relocate_adr_forward: relocated instruction Date: Mon, 18 Mar 2024 14:55:34 +0000 [thread overview] Message-ID: <bug-31507-4717-RkiZhWytOg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31507-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31507 --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- More minimal version: ... $ cat gdb.in file /home/linux/gdb/build/gdb/testsuite/outputs/gdb.arch/disp-step-insn-reloc/disp-step-insn-reloc start break *set_point0 break *set_point1 break *set_point2 break pass break fail set displaced-stepping on continue bt continue bt continue bt continue bt continue bt continue bt $ gdb -q -batch -ex "set trace-commands on" -x gdb.in 2>&1 | tee LOG; grep Breakpoint LOG ... Usually, we have: ... Breakpoint 2, 0x0000aaaaaaaa08bc in can_relocate_b () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:128 Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 Breakpoint 3, 0x0000aaaaaaaa090c in can_relocate_bcond_true () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:164 Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 Breakpoint 4, 0x0000aaaaaaaa0958 in can_relocate_cbz () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:203 Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 ... But once in a while: ... Breakpoint 2, 0x0000aaaaaaaa08bc in can_relocate_b () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:128 Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 Breakpoint 3, 0x0000aaaaaaaa090c in can_relocate_bcond_true () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:164 Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 Breakpoint 4, 0x0000aaaaaaaa0958 in can_relocate_cbz () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:203 ... Looking at the backtrace, we hit pass twice without making progress: ... +continue Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 31 } +bt #0 pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 #1 0x0000aaaaaaaa0928 in can_relocate_bcond_true () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:179 #2 0x0000aaaaaaaa0c9c in main () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:629 +continue Breakpoint 5, pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 31 } +bt #0 pass () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:31 #1 0x0000aaaaaaaa0928 in can_relocate_bcond_true () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:179 #2 0x0000aaaaaaaa0c9c in main () at /home/linux/gdb/src/gdb/testsuite/gdb.arch/insn-reloc.c:629 ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-18 14:55 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-18 12:32 [Bug gdb/31507] New: " vries at gcc dot gnu.org 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 [this message] 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-RkiZhWytOg@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: linkBe 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).