From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 23B9D38460AD; Thu, 10 Nov 2022 14:20:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 23B9D38460AD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668090034; bh=IGFVkL6UL0FUHxEIw69Uwjtz3fifiWQkp1hc+/5Y5rU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ba/oq8llJzrF933qJzLGon18rG1l83oDYmWzeGJzTh+Il2Ko1HSFDBf/D89ZhrOk3 sDFijl/HjbeJqSIBO02GU3aLZHN+y6SbjuPfVqCEdyqZEpC3XhlvjwFHEVuoxZPImi gftqGpehXM4ATIHVdYRghMafeeIZK1+zVBMpQzqY= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/29721] [gdb, record, aarch64] FAIL: gdb.reverse/solib-precsave.exp: reverse-next third shr1 Date: Thu, 10 Nov 2022 14:20:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record 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: 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=3D29721 --- Comment #14 from Tom de Vries --- (In reply to B. Larsen from comment #11) > The oldest gcc I could find was 8.5.0, and it isn't reproducing the issue= . I > don't think I can help with this regression... sorry I created a patch that uses .s files for the two files that use debug info,= so perhaps using those you should be able to reproduce. I understand if you consider this too much of a security risk... --=20 You are receiving this mail because: You are on the CC list for the bug.=