public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "git at jbrengineering dot co.uk" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28405] New: 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 09:45:08 +0000 [thread overview]
Message-ID: <bug-28405-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28405
Bug ID: 28405
Summary: arm-none-eabi: internal-error: ptid_t
remote_target::select_thread_for_ambiguous_stop_reply(
const target_waitstatus*): Assertion
`first_resumed_thread != nullptr' failed
Product: gdb
Version: 11.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: git at jbrengineering dot co.uk
Target Milestone: ---
Created attachment 13691
--> https://sourceware.org/bugzilla/attachment.cgi?id=13691&action=edit
core dump
The changes in
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=8f66807b98f7634c43149ea62e454ea8f877691d
appear to have broken usage with the Black Magic Probe remote debugger.
I'm not familiar with the remote protocol and whether the device should change
but the developer suggests not and I would assume that the gdb changes should
be backwards compatible: https://github.com/blacksphere/blackmagic/issues/929
The problem occurs when trying to attach to a target:
Attaching to Remote target
remote.c:7979: internal-error: ptid_t
remote_target::select_thread_for_ambiguous_stop_reply(const
target_waitstatus*): Assertion `first_resumed_thread != nullptr' failed.
I've attached two core dumps and a capture of gdb.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-01 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 9:45 git at jbrengineering dot co.uk [this message]
2021-10-01 9:45 ` [Bug gdb/28405] " git at jbrengineering dot co.uk
2021-10-01 9:46 ` git at jbrengineering dot co.uk
2021-10-01 9:47 ` git at jbrengineering dot co.uk
2021-10-01 13:48 ` simark at simark dot ca
2021-10-01 15:15 ` git at jbrengineering dot co.uk
2021-10-01 16:56 ` simon.marchi at polymtl dot ca
2021-10-04 12:14 ` simark at simark dot ca
2021-10-04 13:52 ` andrew.burgess at embecosm dot com
2021-10-04 14:10 ` andrew.burgess at embecosm dot com
2021-10-04 15:29 ` andrew.burgess at embecosm dot com
2021-10-04 17:57 ` simark at simark dot ca
2021-10-05 14:20 ` git at jbrengineering dot co.uk
2021-10-06 8:11 ` andrew.burgess at embecosm dot com
2021-10-22 6:42 ` uzytkownik2 at gmail dot com
2021-12-23 12:19 ` cvs-commit at gcc dot gnu.org
2021-12-23 13:17 ` cvs-commit at gcc dot gnu.org
2021-12-23 13:18 ` aburgess at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28405-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).