[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following set and query packets have already been defined.
q
C
-- current thread
Return the current thread id.
Reply:
QC
pid'
q
fThreadInfo
-- all thread ids
q
sThreadInfo
Obtain a list of active thread ids from the target (OS). Since there
may be too many active threads to fit into one reply packet, this query
works iteratively: it may require more than one query/reply sequence to
obtain the entire list of threads. The first query of the sequence will
be the qf
ThreadInfo
query; subsequent queries in the
sequence will be the qs
ThreadInfo
query.
NOTE: replaces the qL
query (see below).
Reply:
m
id'
m
id,id...'
l
'
In response to each query, the target will reply with a list of one or
more thread ids, in big-endian hex, separated by commas. GDB
will respond to each reply with a request for more thread ids (using the
qs
form of the query), until the target responds with l
(lower-case el, for 'last'
).
q
ThreadExtraInfo
,
id -- extra thread info
Where id is a thread-id in big-endian hex. Obtain a printable string description of a thread's attributes from the target OS. This string may contain anything that the target OS thinks is interesting for GDB to tell the user about the thread. The string is displayed in GDB's `info threads' display. Some examples of possible thread extra info strings are "Runnable", or "Blocked on Mutex".
Reply:
q
L
startflagthreadcountnextthread -- query LIST or threadLIST (deprecated)
Obtain thread information from RTOS. Where: startflag (one hex digit) is one to indicate the first query and zero to indicate a subsequent query; threadcount (two hex digits) is the maximum number of threads the response packet can contain; and nextthread (eight hex digits), for subsequent queries (startflag is zero), is returned in the response as argthread.
NOTE: this query is replaced by the q
fThreadInfo
query
(see above).
Reply:
q
M
countdoneargthreadthread...'
remote.c:parse_threadlist_response()
.
q
CRC:
addr,
length -- compute CRC of memory block
Reply:
E
NN'
C
CRC32'
q
Offsets
-- query sect offs
Get section offsets that the target used when re-locating the downloaded
image. Note: while a Bss
offset is included in the
response, GDB ignores this and instead applies the Data
offset to the Bss
section.
Reply:
Text=
xxx;Data=
yyy;Bss=
zzz'
q
P
modethreadid -- thread info request
Returns information on threadid. Where: mode is a hex encoded 32 bit mode; threadid is a hex encoded 64 bit thread ID.
Reply:
See remote.c:remote_unpack_thread_info_response()
.
q
Rcmd,
command -- remote command
command (hex encoded) is passed to the local interpreter for
execution. Invalid commands should be reported using the output string.
Before the final result packet, the target may also respond with a
number of intermediate O
output console output packets.
Implementors should note that providing access to a stubs's
interpreter may have security implications.
Reply:
E
NN'
qSymbol::
-- symbol lookup
Notify the target that GDB is prepared to serve symbol lookup requests. Accept requests from the target for the values of symbols.
Reply:
OK
'
qSymbol:
sym_name'
qSymbol:
sym_value:sym_name message, described below.
qSymbol:
sym_value:sym_name -- symbol value
Set the value of sym_name to sym_value.
sym_name (hex encoded) is the name of a symbol whose value the target has previously requested.
sym_value (hex) is the value for symbol sym_name. If GDB cannot supply a value for sym_name, then this field will be empty.
Reply:
OK
'
qSymbol:
sym_name'
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |