From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: Proposal: qGetTLSAddr remote protocol packet
Date: Fri, 05 Nov 2004 22:44:00 -0000 [thread overview]
Message-ID: <20041105154438.7676aa13@saguaro> (raw)
Below is a proposal for a new remote protocol packet for fetching a
thread local storage address. It is written it in a form (sans markup)
that is compatible with the rest of the remote protocol documentation.
Comments / suggestions?
-------------------
qGetTLSAddr:thread-id:offset:other-param1:other-param2:...:other-paramN
-- get thread local storage address
Fetch the address associated with thread local storage specified
by thread-id, offset, and other-param1 thru other-paramN.
thread-id is the (big endian, hex encoded) thread id associated with the
thread for which to fetch the TLS address.
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.)
other-param1 .. other-paramN are (big endian, hex encoded) OS/ABI
specific data required for fetching the TLS address. For example, a
GNU/Linux system will pass (as other-param1) 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 fields will vary.
Reply:
XX...
Hex encoded (big endian) bytes representing the address of the thread
local storage requested.
E01
The stub-side thread library does not have the required thread local
storage support.
E02
GDB sent a malformed qGetTLSAddr packet to the stub.
E03
The stub was unable to find the thread associated with thread-id.
E04
The stub-side thread library was unable to find the TLS address
associated with thread-id, offset, and the OS/ABI specific
parameters.
Enn (where nn are hex digits and not specfied above)
Some other error occurred.
"" (empty)
An empty reply indicates that qGetTLSAddr is not supported by the stub.
next reply other threads:[~2004-11-05 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 22:44 Kevin Buettner [this message]
2004-11-16 2:09 ` Andrew Cagney
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=20041105154438.7676aa13@saguaro \
--to=kevinb@redhat.com \
--cc=gdb@sources.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