[lldb-dev] format of gdb remote P command with thread id suffix

[Greg Clayton]

Register read example:

$p0;thread:1cb556;#5e
$0000000000000000#00

Register write example:

$P4=00c0030001000000;thread:1cb773;#b7
$OK#00


> On Jun 11, 2014, at 4:49 PM, Todd Fiala <tfiala at google.com> wrote:
> 
> Hey guys,
> 
> What would a gdb remote P command with a thread suffix look like when well formed?  From RNBRemote::ExtractThreadIDFromThreadSuffix (...), it looks like it could be anywhere in the packet as I read HandlePacket_P(...).
> 
> Maybe this?
> P{reg-index-hex}={value-hex}thread:{tid-hex}
> 
> Or is there an expectation of a semi after the value,
> P{reg-index-hex}={value-hex};thread:{tid-hex}?
> 
> Thanks!
> -- 
> Todd Fiala |	 Software Engineer |	 tfiala at google.com |	 650-943-3180
> 
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev