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

Matthew Gardiner mg11 at csr.com
Mon May 12 06:47:03 PDT 2014


>
> Is this omission by design or is it a bug?
I've now found that GDBRemoteCommunicationClient::GetCurrentProcessID() 
has been reworked recently, and that it what has caused the breakage 
I've witnessed.

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.



More information about the lldb-dev mailing list