[Bug python/12967] event.inferior_thread does not exist in all-stop/sync mode

["palves at redhat dot com" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12967

--- Comment #5 from Pedro Alves <palves at redhat dot com> 2012-01-31 17:14:41 UTC ---
> right now I assume that the event handler is supposed to know that the current thread is the stopping thread (if that is even true).

If that's true, it doesn't seem to be documented.  The handler could also know
that is true for non-stop.  This makes it unnecessary and redundant to have
event.inferior_thread in the first place.

If we fixed event.inferior_thread, scripts that are working around this by
looking at the current thread will still work.

> /* thread events can either be thread specific or process wide.  If gdb is
>    running in non-stop mode then the event is thread specific, otherwise
>    it is process wide.

This is really bogus.  A process wide event is something like a process exit,
and is really orthogonal to all-stop/non-stop/itsets.  :-(

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.