From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Implement post_event for Python scripts.
Date: Wed, 28 Jul 2010 14:18:00 -0000 [thread overview]
Message-ID: <4C503BFE.8090608@redhat.com> (raw)
In-Reply-To: <20100727162956.GG13267@adacore.com>
On 27/07/10 17:29, Joel Brobecker wrote:
>> +@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...
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?
I've just regenerated the documentation patch for this reply.
Cheers,
Phil
--
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index be6cd3d..c7e1827 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -20490,6 +20490,37 @@ compute values, for example, it is the only way to get the value of a
convenience variable (@pxref{Convenience Vars}) as a @code{gdb.Value}.
@end defun
+@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}.
+
+@value{GDBN} is not thread-safe. If your Python program uses multiple
+threads, you must be careful to only call @value{GDBN}-specific
+functions in the main @value{GDBN} thread. @code{post_event} ensures
+this. For example:
+
+@smallexample
+(@value{GDBP}) python
+>class Writer():
+> def __init__(self, message):
+> self.message = message;
+> def __call__(self):
+> print self.message
+>
+>gdb.post_event(Writer("Hello"))
+>gdb.post_event(Writer("World"))
+>end
+(@value{GDBP}) Hello
+World
+@end smallexample
+@end defun
+
@findex gdb.write
@defun write string
Print a string to @value{GDBN}'s paginated standard output stream.
next prev parent reply other threads:[~2010-07-28 14:18 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 [this message]
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=4C503BFE.8090608@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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