Re: [rfc] Preferred thread event reporting: Linux native target

[Michael Snyder <msnyder@vmware.com>]

Ulrich Weigand wrote:
> Pedro Alves wrote:
> 
>>> -- this is actually simply the currently selected thread
>>> (i.e. the current value of inferior_ptid).
>> Disagreed.  inferior_ptid will change if an event happens in
>> another thread while you're stepping, but the core decides the event
>> was not a good reason to stop.  E.g., thread hopping.
> 
> Hmm, but if we "thread hop" inferior_ptid should be prefered
> anyway (to get the internal "thread hop" action over with as
> quickly as possible), and afterwards we're back to the thread
> the user is looking at, right?

After that, I think, we're back to whichever thread
the OS decides to schedule next.  I don't think there
is any guarantee that that will be the one the user
was previously looking at.