maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Updated the LLDB qRegisterInfo documentation to contain information on the new "invalidate-regs" and "container-regs" keys that can be returned in response to a qRegisterInfo packet. 

llvm-svn: 173102
This commit is contained in:
Greg Clayton 2013-01-21 23:18:28 +00:00
parent e183597d03
commit 16ed2611f4
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
lldb/docs/lldb-gdb-remote.txt
View File

@ -370,6 +370,36 @@ generic If the register is a generic register that most CPUs have, classify
arg1 - arg8 (specified for registers that contain function
arguments when the argument fits into a register)
container-regs
The value for this key is a comma separated list of decimal register
numbers.
This specifies that this register is contained in other concrete
register values. For example "eax" is in the lower 32 bits of the
"rax" register value for x86_64, so "eax" could specify that it is
contained in "rax" by specifying the register number for "rax".
"container-regs:0,1;"
This is handy for defining what GDB used to call "pseudo" registers.
These registers are never requested by LLDB via the register read
or write packets, the container registers will be requested on behalf
of this register.
invalidate-regs
The value for this key is a comma separated list of decimal register
numbers.
This specifies which register values should be invalidated when this
register is modified.
"invalidate-regs:1,2,3;"
This is handy when modifying a specific register can cause other
register values to change. For example, when debugging an ARM target,
modifying the CPSR register can cause the r8 - r14 and cpsr value to
change depending on if the mode has changed.
//----------------------------------------------------------------------
// "qHostInfo"
//