Re: [PATCHv3] gdb: make thread_info executing and resumed state more consistent

[Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>]

> Simon,
>
> Thanks for the feedback, and sorry for not following up sooner.  This
> got pushed down my list of priorities.
>
> Given how close we are to the GDB 12 branch point, my current plan is to
> wait until shortly after we branch, and then update, retest, and push
> this patch.
>
> That will give us (me) as much time as possible to help resolve any
> problems that this introduces.  I'm expecting there will be some issues
> on the targets I've not tested as much, but hopefully they should be
> easy enough to resolve.
>
> Obviously the above plan can change if people object.

This is fine with me.

I was reminded of this patch because of some bug a colleague hit, which
I recorded here:

  https://sourceware.org/bugzilla/show_bug.cgi?id=28942

In short, the linux-nat target adds threads in the non-resumed state,
and that confuses GDB when a thread hits a breakpoint, that breakpoint
has a condition, and that condition contains an inferior function call.
GDB ends up trying to resume a thread that it thinks is non-resumed but
is actually resumed.

Simon