[lldb-dev] gdb-remote command broken in TOT

Matthew Gardiner mg11 at csr.com
Mon May 12 23:06:08 PDT 2014

Greg Clayton wrote:
> LLDB was incorrectly using the "qC" packet to get the process info. From your old working log:
> $qC#b4
> $QC359b#97
> It now uses the qProcessInfo packet:
>> $qProcessInfo#dc
>> $#00
>> $qProcessInfo#dc
>> $#00
> You should add support for this packet. Here is a sample:
> send packet: $qProcessInfo#00
> read packet: $pid:42a8;parent-pid:42bf;real-uid:ecf;real-gid:b;effective-uid:ecf;effective-gid:b;cputype:7;cpusubtype:3;ostype:macosx;vendor:apple;endian:little;ptrsize:4;#00
> Omit and key value pairs that don't make sense for your target (parent-pid, real-uid, real-gid, effective-uid, effective-gid, cputype, cpusubtype), but do try to at least add the following key/value pairs:
> pid
> triple (with values like: x86_64-apple-macosx, i386-unknown-unknown (for raw binary debugging with no OS like a bare board))
> endian
> ptrsize
> You can omit the "vendor" and "ostype" if you supply the triple.
Thanks for this Greg, I'm on my way with implementing this in my stub.

The problem, which I've previously iterated to Todd, is that now lldb's 
gdb-remote command is incompatible with the stock GNU gdbserver, as it 
knows only of qC and not of qProcessInfo.


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Keep up to date with CSR on our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook, www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at www.twitter.com/CSR_plc.
New for 2014, you can now access the wide range of products powered by aptX at www.aptx.com.

More information about the lldb-dev mailing list