Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Pouget <kevin.pouget@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Python - doc] gdb.post_event description
Date: Tue, 18 Oct 2011 13:32:00 -0000	[thread overview]
Message-ID: <CAPftXUKyqtj3_eEUstd52ioqjHk2hzNVfpeZDaEKD57Jy9xG3w@mail.gmail.com> (raw)
In-Reply-To: <m37h47e4mb.fsf@fleche.redhat.com>

On Fri, Oct 14, 2011 at 9:48 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:
>
> Kevin> according to my experimentations, gdb_do_one_event, which (indirectly)
> Kevin> triggers the processing of Python events posted with gdb.post_event,
> Kevin> is executed right after the prompt has been displayed (and new
> Kevin> charactered fed in), and nowhere else (as far as I could investigate).
>
> Kevin> Does it look right to you?
>
> Yeah, but I would not want to document this too precisely; it is good, I
> think, to have some leeway so we can run the event queue at other times
> if we find the need in the future.

sure,

but I think that the notion of "event" is quite vague here, for
instance we've got Python events, which are totally unrelated to
"post_event" (as far as I understood); and internally there are
inferior events.
(Actually, with that knowledge, I expected 'post_event' events to be
processed more often).

So I think it's important to state when the callback will be
triggered, give the prompt as an example, and mentioned that more
event processing points might be added in the next releases

What do you think about it?

Thanks,

Kevin


  reply	other threads:[~2011-10-18 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12  8:53 Kevin Pouget
2011-10-14 19:49 ` Tom Tromey
2011-10-18 13:32   ` Kevin Pouget [this message]
2011-10-18 13:58     ` Phil Muldoon
2011-10-19 20:45     ` Tom Tromey

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=CAPftXUKyqtj3_eEUstd52ioqjHk2hzNVfpeZDaEKD57Jy9xG3w@mail.gmail.com \
    --to=kevin.pouget@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --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