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

[Todd Fiala]

Hah ok forgot I have client code in LLDB I can look at.  Got my answer.
 "...;thread:{tid-hex}" is what I needed (semi-colon separated).


On Wed, Jun 11, 2014 at 4:51 PM, Todd Fiala <tfiala at google.com> wrote:

> (Well not exactly anywhere - the HandlePacket_P would have already parsed
> out the P{reg-index-hex}={value-hex} portion, so the real question is how
> much content, if any, is expected to come between the end of the parsed hex
> value and the start of the "thread" keyword).
>
>
> On Wed, 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
>>
>
>
>
> --
> Todd Fiala | Software Engineer |  tfiala at google.com |  650-943-3180
>



-- 
Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140611/fc450b26/attachment.html>