From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 480863857810; Fri, 1 Oct 2021 15:15:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 480863857810 From: "git at jbrengineering dot co.uk" To: gdb-prs@sourceware.org Subject: [Bug gdb/28405] arm-none-eabi: internal-error: ptid_t remote_target::select_thread_for_ambiguous_stop_reply(const target_waitstatus*): Assertion `first_resumed_thread != nullptr' failed Date: Fri, 01 Oct 2021 15:15:26 +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.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: git at jbrengineering dot co.uk X-Bugzilla-Status: UNCONFIRMED 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 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2021 15:15:26 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28405 --- Comment #4 from John --- Not that I'm aware of...not ideal I know. It's probably possible to flash a STM32103 in qemu or something with the black magic firmware and remote to t= hat? Not sure how one would then attempt attaching to a target then though. I have checked out the source however so can assist in any suggested fix - I had hoped it might be simple for someone familiar with the codebase, when considering the changes made in that commit. I can attempt some digging myself but some pointers would be helpful. --=20 You are receiving this mail because: You are on the CC list for the bug.=