From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2EFA03854177; Fri, 21 Oct 2022 10:54:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2EFA03854177 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1666349669; bh=Ebh+lDWgiznS0b0VSlGWVbAj8NyJjPgyx8f7n1lkJ5s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vjwDi4kqmgzDRD9IPhDTCykSRio23OsHn6MsshCoUuH/T2E/Te29kAarvrlLF5lwC 7Ejc/eT0cid9Xhq7WrQqxN5A3g4yGhk1oDGA1xmbqsgEuEqONuSHgiw3Hq1b5b1dQk Z953fTDGqjKhsd0peHRmDnvn9QVmDcgKIEVCKUoQ= From: "luis.machado at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug rust/29272] regression: previously OK rust tests crash with SIGILL/SEGV/ABRT on Debian armhf Date: Fri, 21 Oct 2022 10:54:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: rust X-Bugzilla-Version: 11.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: luis.machado at arm dot com X-Bugzilla-Status: ASSIGNED 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_status cc cf_reconfirmed_on everconfirmed 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=3D29272 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED CC| |luis.machado at arm dot com Last reconfirmed| |2022-10-21 Ever confirmed|0 |1 --- Comment #4 from Luis Machado --- Sorry for the delayed reply. I managed to reproduce this on Ubuntu 22.04 with rustc 1.58.1, but I get a SIGSEGV. On Ubuntu 20.04, with rustc 1.57, I get a SIGILL. The gdb's are the same, top-of-trunk. This is an issue with displaced stepping in the Arm port of GDB. If you dis= able it (set displaced-stepping off), the test runs fine. I'll investigate this. --=20 You are receiving this mail because: You are on the CC list for the bug.=