<div dir="ltr"><div>Hey Matthew,</div><div><br></div><div><div>> However is there any real need to restrict the fallback case to just Apple/iOS? </div></div><div><br></div><div>Keep in mind that qC in gdbserver does implement the protocol correctly and returns the thread id, not the proc id. On Linux the first thread happens to get a thread id that is identical to the proc id. So when launching an exe, the active thread id returned just happens to be the proc id as well out of happy coincidence. This is not true on other OSes and not guaranteed true when attaching to a Linux process if the active thread is not the first thread. Given that lldb was not caching the proc id until my change last week, it means that lldb using qC against a gdbserver (or gdb remote protocol implementing qC per spec) is definitely getting the buggy behavior I was fixing (i.e. different proc ids throughout the life of the process when running against a multi-threaded inferior, and entirely invalid results for proc id when run on OSes where the thread ids have no correlation to the proc id, as on MacOSX).</div>
<div><br></div><div>Thus, reverting to using qC when qProcessInfo isn't implemented is really just reverting to buggy and inconsistent behavior, although it may allow lldb to run where it can't now (and could before) and the proc id reported just happens to be right some of the time.</div>
<div><br></div><div>I think the real fix here may be if $qProcessInfo isn't present, then we probably need to settle for not assuming we can get the process id, and just make sure lldb can handle running without it in that case. </div>
<div><br></div><div>Greg, any thoughts on that?</div><div><br></div><div>-Todd</div><div><br></div><div>On Tuesday, May 13, 2014, Matthew Gardiner <<a href="mailto:mg11@csr.com" target="_blank">mg11@csr.com</a>> wrote:e thread if returned <br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Todd Fiala wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
This is a change I made.<br>
<br>
qC is supposed to return the thread id, not the process id.<br>
<br>
qProcessInfo is being used now to collect the process id. We added a fallback so that if the process info request fails, on Apple/iOS we fall back to the older qC (which, as indicated before, used to return the process id erroneously, see the gdb remote documentation).<br>
</blockquote>
<br>
After doing a bit more analysis, I see that you added a fallback such that if the process info request fails, we fall back to traditional gdbserver qC. This is completely reasonable, and permits our custom stubs to support qProcessInfo.<br>
<br>
However is there any real need to restrict the fallback case to just Apple/iOS? that is:<br>
<br>
const llvm::Triple &triple = GetProcessArchitecture().<u></u>GetTriple();<br>
if ((triple.getVendor() == llvm::Triple::Apple) &&<br>
(triple.getOS() == llvm::Triple::IOS))<br>
{<br>
<br>
Surely, all stubs which fail to implement qProcessInfo should be permitted to fallback to qC?<br>
<br>
I've just commented out the above "if" in my working copy, and now the initial "gdb-remote host:port" works again - in so far as the current inferior process number is reported rather than 0. (Admittedly other things don't quite work as desired later on in the debug-session, e.g. "next". But presumably an Apple/iOS stub would either fail similarly, or work as expected due to some localised conditional treatment, (i.e. "if apple then...")).<br>
<br>
So, to continue to interoperate with traditional gdbserver implementations can we let all older stubs continue to fallback to qC?<br>
<br>
thanks<br>
Matt<br>
<br>
<br>
<br>
<br>
<br>
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<br>
More information can be found at <a href="http://www.csr.com" target="_blank">www.csr.com</a>. Keep up to date with CSR on our technical blog, <a href="http://www.csr.com/blog" target="_blank">www.csr.com/blog</a>, CSR people blog, <a href="http://www.csr.com/people" target="_blank">www.csr.com/people</a>, YouTube, <a href="http://www.youtube.com/user/CSRplc" target="_blank">www.youtube.com/user/CSRplc</a>, Facebook, <a href="http://www.facebook.com/pages/CSR/191038434253534" target="_blank">www.facebook.com/pages/CSR/<u></u>191038434253534</a>, or follow us on Twitter at <a href="http://www.twitter.com/CSR_plc" target="_blank">www.twitter.com/CSR_plc</a>.<br>
New for 2014, you can now access the wide range of products powered by aptX at <a href="http://www.aptx.com" target="_blank">www.aptx.com</a>.<br>
</blockquote></div>
</div>