It is easy to trigger these on MacOSX with:
(lldb) log enable gdb-remote packets
(lldb) file /bin/ls
(lldb) b malloc
(lldb) run
This will print out a register read packet. To trigger memory writes:
(lldb) p (int)puts("hello")
Then you will see some individual register writes from the expression parser.
> On Jun 12, 2014, at 9:26 AM, Todd Fiala <[email protected]> wrote:
>
> Thanks, Greg!
>
>
> On Thu, Jun 12, 2014 at 9:22 AM, Greg Clayton <[email protected]> wrote:
> 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 <[email protected]> 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 | [email protected] | 650-943-3180
> >
> > _______________________________________________
> > lldb-dev mailing list
> > [email protected]
> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>
>
>
> --
> Todd Fiala | Software Engineer | [email protected] | 650-943-3180
>
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
