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/29405] New: [gdb,tdep/aarch64] FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=on/off: pc after stepi matches insn addr after syscall
Date: Mon, 25 Jul 2022 15:44:16 +0000	[thread overview]
Message-ID: <bug-29405-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29405

            Bug ID: 29405
           Summary: [gdb,tdep/aarch64] FAIL:
                    gdb.base/step-over-syscall.exp: vfork:
                    displaced=on/off: pc after stepi matches insn addr
                    after syscall
           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 aarch64, I run into:
...
FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=off: pc after stepi
matches insn addr after syscall
FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=on: pc after stepi
matches insn addr after syscall
...

In more detail:
...
(gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=off: syscall
number matches
PASS: gdb.base/step-over-syscall.exp: vfork: displaced=off: find syscall insn
in vfork
x/2i $pc^M
=> 0xfffff7e31c0c <vfork+12>:   svc     #0x0^M
   0xfffff7e31c10 <vfork+16>:   cmn     x0, #0xfff^M
(gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=off: pc
before/after syscall instruction
stepi^M
[Detaching after vfork from child process 8493]^M
0x0000fffff7e31c14 in vfork () from /lib64/libc.so.6^M
1: x/i $pc^M
=> 0xfffff7e31c14 <vfork+20>:   b.cs    0xfffff7e31c1c <vfork+28>  // b.hs,
b.nlast^M
(gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=off: stepi vfork
insn
print /x $pc^M
$2 = 0xfffff7e31c14^M
(gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=off: pc after
stepi
FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=off: pc after stepi
matches insn addr after syscall
...

I suppose the test-case expects to land on the cmn insn, but instead it lands
on  the next insn.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-07-25 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 15:44 vries at gcc dot gnu.org [this message]
2022-07-25 15:44 ` [Bug tdep/29405] " vries at gcc dot gnu.org
2022-07-25 16:20 ` luis.machado at arm dot com
2022-07-25 16:21 ` luis.machado at arm dot com
2022-07-25 16:27 ` vries at gcc dot gnu.org
2022-07-25 16:41 ` luis.machado at arm dot com
2022-07-25 16:41 ` 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-29405-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).