Debugging with GDB: Thread List Format |
---|
Next: Traceframe Info Format, Previous: Memory Map Format, Up: Remote Protocol [Contents][Index]
To efficiently update the list of threads and their attributes, GDB issues the ‘qXfer:threads:read’ packet (see qXfer threads read) and obtains the XML document with the following structure:
<?xml version="1.0"?> <threads> <thread id="id" core="0" name="name"> ... description ... </thread> </threads>
Each ‘thread’ element must have the ‘id’ attribute that identifies the thread (see thread-id syntax). The ‘core’ attribute, if present, specifies which processor core the thread was last executing on. The ‘name’ attribute, if present, specifies the human-readable name of the thread. The content of the of ‘thread’ element is interpreted as human-readable auxiliary information. The ‘handle’ attribute, if present, is a hex encoded representation of the thread handle.