From a3be24ad59d683d1b08df28e093739743a7cf256 Mon Sep 17 00:00:00 2001 From: Tim Wiederhake Date: Tue, 2 May 2017 11:35:54 +0200 Subject: Python: Remove ptid from gdb.Record interface As discussed here: https://sourceware.org/ml/gdb-patches/2017-04/msg00166.html --- gdb/doc/python.texi | 7 ------- 1 file changed, 7 deletions(-) (limited to 'gdb/doc/python.texi') diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi index ce5810e..8c246a4 100644 --- a/gdb/doc/python.texi +++ b/gdb/doc/python.texi @@ -3110,13 +3110,6 @@ currently active. All record objects become invalid after this call. A @code{gdb.Record} object has the following attributes: -@defvar Record.ptid -ID of the thread associated with this object as a tuple of three integers. The -first is the Process ID (PID); the second is the Lightweight Process ID (LWPID), -and the third is the Thread ID (TID). Either the LWPID or TID may be 0, which -indicates that the operating system does not use that identifier. -@end defvar - @defvar Record.method A string with the current recording method, e.g.@: @code{full} or @code{btrace}. -- cgit v1.1