From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A9FC2385840C; Wed, 6 Sep 2023 04:08:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A9FC2385840C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1693973284; bh=Ve7AfSnZdhQm61J0uJkgQx2pj1ZqmnKa/YNbgRtzYR0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FoUren6uXSBlipz1Am8YdMCITU6QMjwwj6vgk/Zf1KbZqYuMXH9TY8PH5fs7vADzq wVVl4xMe08h4N9VZkewCG+xhp6TkpmcF0D1EWDUc1WIZvC5hSBxxtt8lMmLeDi944N u8xJN2BPfhv0x6NHPiYJVZ6uG3wZOTSn5HY2i3O0= From: "gdbsourceware.3k5z5 at passmail dot net" To: gdb-prs@sourceware.org Subject: [Bug gdb/28874] arm-none-eabi: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed Date: Wed, 06 Sep 2023 04:08:03 +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: 11.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gdbsourceware.3k5z5 at passmail dot net X-Bugzilla-Status: WAITING 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 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=3D28874 fidgetingbits changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gdbsourceware.3k5z5@passmai | |l.net --- Comment #19 from fidgetingbits --- I run into this same issue on the latest version of gdb (13.2 at the time of writing) and gdbserver when debugging various remote 32-bit ARM targets, specifically when using pwndbg loaded (sets up various event hooks). Also worth noting that after gdb crashes, if you restart gdb and re-attach a second time without restarting the target process, the attach works correct= ly. My solution has always been to just automatically restart gdb on crash and re-attach from a shell script. I've confirmed that using the patch provided by John Whittington addresses = the problem. Would be nice to get this fixed as pwndbg users wishing to remotely debug an ARM target will run into this issue. Happy to provide any debug information needed. --=20 You are receiving this mail because: You are on the CC list for the bug.=