Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Phil Muldoon <pmuldoon@redhat.com>,
	       gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Implement post_event for Python scripts.
Date: Fri, 30 Jul 2010 21:43:00 -0000	[thread overview]
Message-ID: <m3sk303au4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100728173128.GM13267@adacore.com> (Joel Brobecker's message of	"Wed, 28 Jul 2010 10:31:28 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

>> Providing an example of a multi-threaded python script using
>> post_event would be too complex for the manual (I'm not sure that was
>> what you wanted anyway).  I provided a small example that shows usage.
>> Is this okay?

Joel> I'm just trying to figure out how this feature can be useful, and
Joel> in particular when the callbacks are triggered. Perhaps, rather than
Joel> an example, what we need is a section that describes the event loop
Joel> and when it is queried.

For the purposes of post_event, I think it is probably sufficient to say
that the callback will be executed in the main thread "sometime".  I
don't think we can really provide anything more concrete than that
anyhow.

Tom


  reply	other threads:[~2010-07-30 21:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 18:53 Phil Muldoon
2010-07-20 19:08 ` Tom Tromey
2010-07-27 16:30 ` Joel Brobecker
2010-07-28 14:18   ` Phil Muldoon
2010-07-28 17:31     ` Joel Brobecker
2010-07-30 21:43       ` Tom Tromey [this message]
2010-08-03 14:26         ` Phil Muldoon
2010-08-03 17:00           ` Eli Zaretskii
2010-08-11 18:35           ` Tom Tromey
2010-08-11 19:05             ` Joel Brobecker
2010-08-11 21:08             ` Phil Muldoon
2010-07-28 17:49     ` Eli Zaretskii
2010-08-18 13:46 ` Pedro Alves
2010-08-18 14:36   ` Daniel Jacobowitz
2010-08-18 17:39     ` Pedro Alves
2010-08-18 18:13   ` Tom Tromey
2010-08-20  0:35     ` Pedro Alves

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=m3sk303au4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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