From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ADDF7383A343; Mon, 25 Jul 2022 15:44:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ADDF7383A343 From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2022 15:44:16 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29405 Bug ID: 29405 Summary: [gdb,tdep/aarch64] FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=3Don/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=3Doff: pc after stepi matches insn addr after syscall FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=3Don: pc after stepi matches insn addr after syscall ... In more detail: ... (gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=3Doff: syscall number matches PASS: gdb.base/step-over-syscall.exp: vfork: displaced=3Doff: find syscall = insn in vfork x/2i $pc^M =3D> 0xfffff7e31c0c : svc #0x0^M 0xfffff7e31c10 : cmn x0, #0xfff^M (gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=3Doff: 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 =3D> 0xfffff7e31c14 : b.cs 0xfffff7e31c1c // b.h= s, b.nlast^M (gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=3Doff: stepi v= fork insn print /x $pc^M $2 =3D 0xfffff7e31c14^M (gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=3Doff: pc after stepi FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=3Doff: pc after stepi matches insn addr after syscall ... I suppose the test-case expects to land on the cmn insn, but instead it lan= ds on the next insn. --=20 You are receiving this mail because: You are on the CC list for the bug.=