Re: [patch] Support inferior events in python

Jan Kratochvil
2011-07-07T13:51:13Z

On Thu, 07 Jul 2011 15:45:14 +0200, sami wagiaalla wrote:
> On 07/06/2011 03:37 PM, Jan Kratochvil wrote:
> > As Pedro asked
> > http://sourceware.org/ml/gdb-patches/2011-02/msg00213.html
> > > Actually, do you really need non-stop?
> >
> > I also do not think the testcases should / need to test the non-stop mode.
> > But currently it cannot test thread id in all-stop/sync mode, therefore I have
> > filed it as PR and kept the testcases in non-stop/async mode:
> > http://sourceware.org/bugzilla/show_bug.cgi?id=12967
>
> Yes, as you have concluded non-stop/async was needed to test thread
> id. It did not even occur to me that thread id should be available
> on all-stop because all threads are actually stopped. The event
> expresses that all threads are stopped by not setting thread id.

I still believe event.inferior_thread should be there even in all-stop/sync
mode, the event occured for that thread. Whether the Python script can find
out the information also elsewhere or not I do not think that matters.

Sure it is more about some design style than any real bug so there can be
different opinions. That PR python/12967 above is up to Phil now.

Thanks,
Jan