From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/7] Documentation for Inferior.thread_from_thread_handle
Date: Wed, 19 Jul 2017 02:33:00 -0000 [thread overview]
Message-ID: <83zic1b1fx.fsf@gnu.org> (raw)
In-Reply-To: <20170718175503.6023ec04@pinnacle.lan> (message from Kevin Buettner on Tue, 18 Jul 2017 17:55:03 -0700)
> Date: Tue, 18 Jul 2017 17:55:03 -0700
> From: Kevin Buettner <kevinb@redhat.com>
>
> gdb/doc/ChangeLog:
>
> * python.texi (Inferiors In Python): Add description for method
> Inferior.thread_from_thread_handle.
> ---
> gdb/doc/python.texi | 7 +++++++
> 1 file changed, 7 insertions(+)
OK, thanks.
next prev parent reply other threads:[~2017-07-19 2:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 0:42 [PATCH v3 0/7] Thread handle to thread info mapping Kevin Buettner
2017-07-19 0:54 ` [PATCH v3 2/7] Add `thread_from_thread_handle' method to (Python) gdb.Inferior Kevin Buettner
2017-07-23 20:53 ` Simon Marchi
2017-07-19 0:54 ` [PATCH v3 1/7] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2017-07-23 20:39 ` Simon Marchi
2017-07-19 0:55 ` [PATCH v3 4/7] Test case for Inferior.thread_from_thread_handle Kevin Buettner
2017-07-23 21:17 ` Simon Marchi
2017-07-19 0:55 ` [PATCH v3 5/7] Add thread_db_notice_clone to gdbserver Kevin Buettner
2017-07-23 21:27 ` Simon Marchi
2017-07-19 0:55 ` [PATCH v3 3/7] Documentation for Inferior.thread_from_thread_handle Kevin Buettner
2017-07-19 2:33 ` Eli Zaretskii [this message]
2017-07-19 0:56 ` [PATCH v3 7/7] Documentation for qXfer:threads:read handle attribute Kevin Buettner
2017-07-19 2:34 ` Eli Zaretskii
2017-07-19 0:56 ` [PATCH v3 6/7] Add thread_handle_to_thread_info support for remote targets Kevin Buettner
2017-07-23 21:47 ` Simon Marchi
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=83zic1b1fx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).