From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 3/4] Documentation for gdb.thread_from_thread_handle
Date: Thu, 05 May 2016 21:17:00 -0000 [thread overview]
Message-ID: <20160505141647.65c13e73@pinnacle.lan> (raw)
In-Reply-To: <20160505140938.26a084ed@pinnacle.lan>
gdb/doc/ChangeLog:
* python.texi (Threads In Python): Add description for function
gdb.thread_from_thread_handle.
---
gdb/doc/python.texi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index ffbf89a..c519d1c 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -2981,6 +2981,13 @@ This function returns the thread object for the selected thread. If there
is no selected thread, this will return @code{None}.
@end defun
+@findex gdb.thread_from_thread_handle
+@defun gdb.thread_from_thread_handle
+Return the thread object corresponding to the thread handle,
+@var{thread_handle}, a thread library specific data structure such as
+@code{pthread_t} for pthreads library implementations.
+@end defun
+
A @code{gdb.InferiorThread} object has the following attributes:
@defvar InferiorThread.name
next prev parent reply other threads:[~2016-05-05 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 21:09 [PATCH 0/4] Thread handle to (GDB internal) thread object mapping Kevin Buettner
2016-05-05 21:12 ` [PATCH 1/4] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2016-05-05 21:14 ` [PATCH 2/4] Add `thread_from_thread_handle' function to (Python) gdb module Kevin Buettner
2016-05-05 21:17 ` Kevin Buettner [this message]
2016-05-06 6:31 ` [PATCH 3/4] Documentation for gdb.thread_from_thread_handle Eli Zaretskii
2016-05-06 6:32 ` Eli Zaretskii
2016-05-05 21:19 ` [PATCH 4/4] Test case " Kevin Buettner
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=20160505141647.65c13e73@pinnacle.lan \
--to=kevinb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).