[lldb-dev] format of gdb remote P command with thread id suffix
Todd Fiala
tfiala at google.com
Thu Jun 12 09:47:56 PDT 2014
Great, thanks Greg.
On Thu, Jun 12, 2014 at 9:34 AM, Greg Clayton <gclayton at apple.com> wrote:
> 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 <tfiala at google.com> wrote:
> >
> > Thanks, Greg!
> >
> >
> > On Thu, Jun 12, 2014 at 9:22 AM, Greg Clayton <gclayton at apple.com>
> 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 <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
> >
> >
> >
> >
> > --
> > 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/20140612/9cf27b76/attachment.html>
More information about the lldb-dev
mailing list