This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Support inferior events in python
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: sami wagiaalla <swagiaal at redhat dot com>
- Cc: Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org, Tom Tromey <tromey at redhat dot com>, Phil Muldoon <pmuldoon at redhat dot com>
- Date: Thu, 7 Jul 2011 15:50:46 +0200
- Subject: Re: [patch] Support inferior events in python
- References: <m37he0g95v.fsf@fleche.redhat.com> <20110209163022.GA16069@host1.dyn.jankratochvil.net> <4D55559B.1090004@redhat.com> <201102111556.42026.pedro@codesourcery.com> <4D59662D.30101@redhat.com> <20110216111054.GA3594@host1.dyn.jankratochvil.net> <20110706193742.GA4463@host1.jankratochvil.net> <4E15B86A.1090701@redhat.com>
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