Re: [RFA 1/3] Add new_inferior, inferior_deleted, and new_thread events

Simon Marchi
2017-09-09T21:09:29Z

On 2017-09-09 22:41, Tom Tromey wrote:
> I can just make this not be a subclass of ThreadEvent and then clean up
> the docs. Though, there's a PR open about ThreadEvent.inferior_thread
> not being set in the all-stop case.
>
> Tom

I am not sure I understand. Making NewThreadEvent a subclass of
ThreadEvent makes sense to me, since it is an event that concerns one
thread. Right now inferior_thread field of ThreadEvent subclasses is
always None in all-stop, but I don't think it has to stay that way for
new events we introduce (changing the behavior of existing events should
be done more carefully, of course).

Simon