Change the container-regs kv pair in the qRegsiterInfo

reply to be hex encoded, not decimal.

Fix the whitespace in the container-regs/invalidate-regs
documentation, fix one ambiguous hex/decimal number in an
example.

llvm-svn: 173225
This commit is contained in:
Jason Molenda 2013-01-23 04:38:32 +00:00
parent 243bc85355
commit fa85ca5fff
2 changed files with 42 additions and 42 deletions
lldb
docs
tools/debugserver/source

View File

@ -400,7 +400,7 @@ invalidate-regs
This specifies which register values should be invalidated when this
register is modified. For example if modifying "eax" would cause "rax",
"eax", "ax", "ah", and "al" to be modified where rax is 0x0, eax is 15,
"eax", "ax", "ah", and "al" to be modified where rax is 0x0, eax is 0x15,
ax is 0x25, ah is 0x35, and al is 0x39, the "invalidate-regs" key/value
pair would be:

View File

@ -1560,7 +1560,7 @@ RNBRemote::HandlePacket_qRegisterInfo (const char *p)
{
if (i > 0)
ostrm << ',';
ostrm << DECIMAL << reg_entry->nub_info.pseudo_regs[i];
ostrm << RAW_HEXBASE << reg_entry->nub_info.pseudo_regs[i];
}
ostrm << ';';
}