From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21013 invoked by alias); 6 Dec 2004 20:59:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20517 invoked from network); 6 Dec 2004 20:58:26 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 6 Dec 2004 20:58:26 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iB6KwPZ1000508 for ; Mon, 6 Dec 2004 15:58:26 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iB6KwPr25885 for ; Mon, 6 Dec 2004 15:58:25 -0500 Received: from localhost.localdomain (vpn50-35.rdu.redhat.com [172.16.50.35]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id iB6KwPGE010372 for ; Mon, 6 Dec 2004 15:58:25 -0500 Received: from ironwood.lan (ironwood.lan [192.168.64.8]) by localhost.localdomain (8.12.11/8.12.10) with SMTP id iB6KwKah014745 for ; Mon, 6 Dec 2004 13:58:20 -0700 Date: Mon, 06 Dec 2004 21:31:00 -0000 From: Kevin Buettner To: gdb-patches@sources.redhat.com Subject: [RFA] Add qGetTLSAddr packet documentation to gdb.texinfo Message-ID: <20041206135819.426723ee.kevinb@redhat.com> Organization: Red Hat Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00169.txt.bz2 The patch below adds documentation for the qGetTLSAddr packet to gdb.texinfo. The text that this patch adds, stripped of markup, is the same as that contained in the following proposal: http://sources.redhat.com/ml/gdb/2004-11/msg00189.html . Eli has already approved this text for inclusion in the GDB manual. However, that text didn't contain the necessary markup, nor did it indicate where it would be placed within the overall document. Still okay? * gdb.texinfo (General Query Packets): Document qGetTLSAddr packet. Index: doc/gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.227 diff -u -p -r1.227 gdb.texinfo --- doc/gdb.texinfo 23 Nov 2004 12:12:15 -0000 1.227 +++ doc/gdb.texinfo 6 Dec 2004 20:35:02 -0000 @@ -21071,6 +21071,40 @@ Requests of this form may be added in th not recognize the @var{object} keyword, or its support for @var{object} does not recognize the @var{operation} keyword, the stub must respond with an empty packet. + +@item @code{qGetTLSAddr}:@var{thread-id},@var{offset},@var{load-module-param-1},@dots,@var{load-module-param-N} --- get thread local storage address + +Fetch the address associated with thread local storage specified +by @var{thread-id}, @var{offset}, and @var{load-module-param-1} thru @var{load-module-param-N}. + +@var{thread-id} is the (big endian, hex encoded) thread id associated with the +thread for which to fetch the TLS address. + +@var{offset} is the (big endian, hex encoded) offset associated with the +thread local variable. (This offset is obtained from the debug +information associated with the variable.) + +@var{load-module-param-1} thru @var{load-module-param-N} are (big endian, hex +encoded) data which represent an OS/ABI specific encoding of the load +module. For example, a @sc{GNU}/Linux system will pass (as +@var{load-module-param-1}) the link map address of the shared object +associated with the thread local storage under consideration. Other +operating environments may require different data, so the precise +meaning of these parameters will vary. + +Reply: +@table @asis +@item @var{XX@dots} +Hex encoded (big endian) bytes representing the address of the thread +local storage requested. + +@item @code{E}@var{nn} (where @var{nn} are hex digits) +An error occurred. + +@item @code{""} (empty) + An empty reply indicates that @code{qGetTLSAddr} is not supported by the stub. +@end table + @end table @node Register Packet Format