From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A36343896C34; Mon, 5 Dec 2022 10:03:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A36343896C34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670234602; bh=qejEOaNpy1xRgF8nLv+GLE2UmkJ6A3w0vrf1pyRpSfQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QC9QJETakzA2yM3m0RWa4XIYofyaK5L/JhggTjNeOFPG/tx12OEAMekg8xB3c/p/G ebMOsZTwqL7Yp3ai7XYx5P+rZ4nkbIvAbZ9VVoE2xQI8EpVkEAWSX66BUWi2SPjlX1 ltMw5o6+7ibM6NpdKeL3ywg3Ar/RMeOBge23wnIQ= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/29850] [gdb, powerpc64le] FAIL: gdb.base/longjmp.exp: next over longjmp(1) Date: Mon, 05 Dec 2022 10:03:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 12.1 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: 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=3D29850 --- Comment #2 from Tom de Vries --- (In reply to Tom de Vries from comment #1) > However, I noticed when trying the same on x86_64: > ... > (gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1) > next^M > 56 resumes++;^M > (gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1) > ... > which is a nicer failure mode, given that we stop at the first line after > the longjmp target. >=20 And that's the failure mode reported in PR26967. --=20 You are receiving this mail because: You are on the CC list for the bug.=