From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C2A013858C74; Thu, 29 Sep 2022 15:22:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C2A013858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1664464929; bh=xtzWs3+M85yo9svAaRarO+3ySKwGqgpTrW/RvmQwcgI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ywgeyKJPHYONqNvqneefubKCeplyGIQfeHoVO8qrXdmEe8tFDjnbmmGTMb8dq9u9O S7xuGAmWzorHpuEaUHAmJVz/S6q3SRpBHGQHMRbQtNn7boFEJ2At9n25RCDFEI+v2G 4KCJ00G+fRY3b4buZ7h1VBqZgnhNASrBIOuqd5II= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/26761] thread.c:95: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed Date: Thu, 29 Sep 2022 15:22:09 +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: unknown 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=3D26761 --- Comment #14 from Tom de Vries --- (In reply to Tom de Vries from comment #13) > (In reply to Simon Marchi from comment #11) > > Is it possible that this series here is addressing this bug? > >=20 > > https://inbox.sourceware.org/gdb-patches/20220227000051.3336149-1- > > kevinb@redhat.com/ >=20 > Ack, let me check. I build gdb-12.1-release tag, reproduced the problem, then applied the patch series, rebuild, and no more problem. --=20 You are receiving this mail because: You are on the CC list for the bug.=