From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Export gdb.block_signals and create gdb.Thread
Date: Tue, 04 Jul 2023 20:05:19 +0300 [thread overview]
Message-ID: <83wmzfk3ow.fsf@gnu.org> (raw)
In-Reply-To: <20230704165113.409751-1-tom@tromey.com> (message from Tom Tromey on Tue, 4 Jul 2023 10:51:13 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Tue, 4 Jul 2023 10:51:13 -0600
> While working on an experiment, I realized that I needed the DAP
> block_signals function. I figured other developers may need it as
> well, so this patch moves it from DAP to the gdb module and exports
> it.
>
> I also added a new subclass of threading.Thread that ensures that
> signals are blocked in the new thread.
>
> Finally, this patch slightly rearranges the documentation so that
> gdb-side threading issues and functions are all discussed in a single
> node.
> ---
> gdb/NEWS | 6 ++
> gdb/doc/python.texi | 105 +++++++++++++++++++-----------
> gdb/python/lib/gdb/__init__.py | 32 +++++++++
> gdb/python/lib/gdb/dap/startup.py | 26 +-------
> 4 files changed, 106 insertions(+), 63 deletions(-)
OK for the documentation parts, thanks.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-07-04 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 16:51 Tom Tromey
2023-07-04 17:05 ` Eli Zaretskii [this message]
2023-07-23 21:07 ` 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=83wmzfk3ow.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).