From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8E7C63858C50; Mon, 18 Mar 2024 15:11:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8E7C63858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710774712; bh=M15ANQibq2v7+xDBd9eCUeawMjYndlu//63IpiTPHTA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=h/aSP+XHWTxo3IKhOHkzG1oQbXMZ9hNnWIp1WlN7JhFuRc2F+W3Enew3WBxgH7vZW a5Qu6IdqOWCskiTpV3ygOIVjwFYuKR3uGloOpjZ8bSL29qbgv82sYk5c/u2BH8OAzT Gbr/q1Ua3CX9MnzCeANNH/JQ/ZVIA8iurLCUHAfE= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/31507] [gdb, aarch64] FAIL: gdb.arch/disp-step-insn-reloc.exp: can_relocate_adr_forward: relocated instruction Date: Mon, 18 Mar 2024 15:11:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed 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: cc component Message-ID: In-Reply-To: References: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31507 Tom de Vries changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luis.machado at arm dot com Component|gdb |tdep --- Comment #7 from Tom de Vries --- This may be a regression due to: ... commit 0c27188999bfc5bf03536bf44593c4ed8df296c3 Author: Luis Machado Date: Thu Jan 9 16:04:36 2020 -0300 Fix step-over-syscall.exp failure In particular, this one: FAIL: gdb.base/step-over-syscall.exp: fork: displaced=3Don: check_pc_after_cross_syscall: single step over fork final pc When ptrace fork event reporting is enabled, GDB gets a PTRACE_EVENT_FO= RK event whenever the inferior executes the fork syscall. Then the logic is that GDB needs to step the inferior yet again in orde= r to receive a predetermined SIGTRAP, but no execution takes place because t= he signal was already queued for delivery. That means the PC should stay t= he same. I noticed the aarch64 code is currently adjusting the PC in this situat= ion, making the inferior skip an instruction without executing it. The following change checks if we did not execute the instruction (pc - to =3D=3D 0), making proper adjustments for such case. Regression tested on aarch64-linux-gnu on the tryserver. gdb/ChangeLog: 2020-01-21 Luis Machado ... Luis, could you take a look? --=20 You are receiving this mail because: You are on the CC list for the bug.=