From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 38564385703F; Mon, 28 Nov 2022 13:23:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 38564385703F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669641819; bh=5so6Nj08unFpiiSP3ziSCT6Lpo6cBt4vTji4BNyuuXM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Kjyw+WYp6uP6JgVwQnxP4DzT+QDxHHJZZmbDGzGtjQoTggKsZLrwAGxP92YsMfBcy 5ju9kc3flVB89clLdbe2/1PogxViIXuryDWsa9c0vgVCwB0/x3AtpVcGgs1yrrAU/e 3tr9/GAmDRihH9KsTsxT/NKeMi6ogzpf6C4LTHa4= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/29792] [gdb/testsuite, powerpc] FAIL: gdb.opt/solib-intra-step.exp: second-hit Date: Mon, 28 Nov 2022 13:23:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit 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: 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=3D29792 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom de Vries : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D76cd77dc729b= 03d6b33c683323594479e33a3f9a commit 76cd77dc729b03d6b33c683323594479e33a3f9a Author: Tom de Vries Date: Mon Nov 28 14:23:34 2022 +0100 [gdb/testsuite] Fix gdb.opt/solib-intra-step.exp for powerpc64le On powerpc64le-linux, I run into: ... (gdb) PASS: gdb.opt/solib-intra-step.exp: first-hit step^M 28 { /* first-retry */^M (gdb) FAIL: gdb.opt/solib-intra-step.exp: second-hit ... It's a bit easier to understand what happens if we do a full stepping session: ... Temporary breakpoint 1, main () at solib-intra-step-main.c:23 23 shlib_first (); (gdb) step shlib_first () at solib-intra-step-lib.c:29 29 shlib_second (0); /* first-hit */ (gdb) step 28 { /* first-retry */ (gdb) step 29 shlib_second (0); /* first-hit */ (gdb) step shlib_second (dummy=3D0) at solib-intra-step-lib.c:23 23 abort (); /* second-hit */ ... and compare that to the line info: ... CU: solib-intra-step-lib.c: File name Line number Starting address View=20= =20=20 Stmt solib-intra-step-lib.c 22 0x710=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c 23 0x724=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c 28 0x740=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c 29 0x74c=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c 28 0x750=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c 29 0x758=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c 30 0x760=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 x solib-intra-step-lib.c - 0x77c ... So we step from line 29 to line 28, and back to line 29, which is behav= iour that matches the line table. The peculiar order is due to using optimization. The problem is that the test-case doesn't expect this order. Fix this by allowing this order in the test-case. Tested on powerpc64le-linux. PR testsuite/29792 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29792 --=20 You are receiving this mail because: You are on the CC list for the bug.=