[PATCH v3 1/5] gdb: make the remote target track its own thread resume state

Simon Marchi simon.marchi@efficios.com
Mon Jan 18 13:53:57 GMT 2021



On 2021-01-18 5:36 a.m., Sebastian Huber wrote:
> Thanks for the hint, I will have a look at it, but it may take a while.
> 
> I noticed another issue on nios2-rtems built on openSUSE:
> 
> ../../sourceware-mirror-binutils-gdb-edf0f28/gdb/remote.c:7820: internal-error: ptid_t remote_target::select_thread_for_ambiguous_stop_reply(const target_waitstatus*): Assertion `first_resumed_thread != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> 
> It worked with the GDB commit 4180301.

Please see this comment (an proposed fix), I think you are hitting the same issue:

https://sourceware.org/bugzilla/show_bug.cgi?id=26819#c20

Simon


More information about the Gdb-patches mailing list