From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Implement post_event for Python scripts.
Date: Tue, 27 Jul 2010 16:30:00 -0000 [thread overview]
Message-ID: <20100727162956.GG13267@adacore.com> (raw)
In-Reply-To: <4C45F0B0.5000903@redhat.com>
> +@findex gdb.post_event
> +@defun post_event event
> +Put @var{event}, a callable object taking no arguments, into
> +@value{GDBN}'s internal event queue. This callable will be invoked at
> +some later point, during @value{GDBN}'s event processing. Events
> +posted using @code{post_event} will be run in the order in which they
> +were posted; however, there is no way to know when they will be
> +processed relative to other events inside @value{GDBN}.
Would it be useful to provide an exemple of how this feature could
be used? It does not seem obvious, and I am not sure without reading
the GDB Manual that users are familiar with GDB's internal even queue...
--
Joel
next prev parent reply other threads:[~2010-07-27 16:30 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 [this message]
2010-07-28 14:18 ` Phil Muldoon
2010-07-28 17:31 ` Joel Brobecker
2010-07-30 21:43 ` Tom Tromey
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=20100727162956.GG13267@adacore.com \
--to=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