Todd Fiala wrote:
Okay, looking back at your packet log:
127.000.000.001.07778-127.000.000.001.43138: $#00
127.000.000.001.43138-127.000.000.001.07778: $qProcessInfo#dc
127.000.000.001.07778-127.000.000.001.43138: $#00
127.000.000.001.43138-127.000.000.001.07778: $qProcessInfo#dc
127.000.000.001.07778-127.000.000.001.43138: $#00
Couple options here:
1. implement qProcessInfo in your custom remote monitor. The only
key-value pair we're looking for in this case is the pid:{process-id}
pair as far as retrieving the process id goes. If you're in control
of the remote, this will be your fastest option for getting a resolution.
Thanks Todd,
I'm on my way to implement qProcessInfo in my stub.
The real problem is that, the log I sent was between lldb and the linux
gdbserver from FC20. And so now lldb is no longer compatible with the
older reference implementation of gdbserver. Is this intentional?
Matt
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.
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
