From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>,
Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [patch] Support inferior events in python
Date: Thu, 07 Jul 2011 14:03:00 -0000 [thread overview]
Message-ID: <20110707135046.GA20307@host1.jankratochvil.net> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-07-07 13:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 15:54 sami wagiaalla
2011-01-04 18:22 ` Eli Zaretskii
2011-01-04 20:09 ` Tom Tromey
2011-01-17 22:59 ` sami wagiaalla
2011-01-19 16:42 ` Tom Tromey
2011-01-21 23:06 ` sami wagiaalla
2011-01-28 16:21 ` Tom Tromey
2011-02-02 21:04 ` sami wagiaalla
2011-02-02 21:35 ` Tom Tromey
2011-02-03 16:41 ` sami wagiaalla
2011-02-03 18:26 ` Eli Zaretskii
2011-02-03 19:45 ` sami wagiaalla
2011-02-03 21:42 ` Tom Tromey
2011-02-04 20:07 ` sami wagiaalla
2011-02-04 20:29 ` Tom Tromey
2011-02-04 20:35 ` sami wagiaalla
2011-02-04 23:00 ` Paul Pluzhnikov
2011-02-05 5:44 ` Hui Zhu
2011-02-07 15:22 ` sami wagiaalla
2011-02-07 15:24 ` Tom Tromey
2011-02-07 15:34 ` Paul Pluzhnikov
2011-02-07 16:01 ` sami wagiaalla
2011-02-07 15:39 ` sami wagiaalla
2011-04-20 20:26 ` Patch for non-stop remote assertion (was: RE: [patch] Support inferior events in python) Marc Khouzam
2011-04-25 18:12 ` Patch for non-stop remote assertion Tom Tromey
2011-04-25 18:31 ` Marc Khouzam
2011-05-16 15:41 ` Marc Khouzam
2011-05-19 18:38 ` Tom Tromey
2011-02-09 7:55 ` [patch] Support inferior events in python Jan Kratochvil
2011-02-09 16:19 ` sami wagiaalla
2011-02-09 16:30 ` Jan Kratochvil
2011-02-11 15:28 ` sami wagiaalla
2011-02-11 15:55 ` Joel Brobecker
2011-02-11 19:19 ` sami wagiaalla
2011-02-11 19:46 ` Jan Kratochvil
2011-02-11 15:57 ` Pedro Alves
2011-02-14 17:36 ` sami wagiaalla
2011-02-16 11:48 ` Jan Kratochvil
2011-07-06 19:42 ` Jan Kratochvil
2011-07-07 13:51 ` sami wagiaalla
2011-07-07 14:03 ` Jan Kratochvil [this message]
2011-09-13 21:45 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110707135046.GA20307@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=pmuldoon@redhat.com \
--cc=swagiaal@redhat.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).