Great thanks. Will put it in now.
On Wed, May 7, 2014 at 11:34 AM, Greg Clayton <[email protected]> wrote: > Looks good! > > On May 7, 2014, at 11:15 AM, Todd Fiala <[email protected]> wrote: > > > Modify debugserver to follow gdb remote $qC protocol definition. > > > > $qC from debugserver now returns the current thread's thread-id (and, > like $?, will set a current thread if one is not already selected). > Previously it was returning the current process id. > > > > lldb will now query $qProcessInfo to retrieve the process id. The > process id is now cached lazily and reset like other cached values. > Retrieval of the process id will fall back to the old $qC method for > vendor==Apple and os==iOS if the qProcessInfo retrieval fails. > > > > Added a gdb remote protocol-level test to verify that $qC immediately > after a launched inferior returns the same thread reported by $?. Verifies > the given process id is a currently valid process on host OSes for which we > know how to check (MacOSX, Linux, {Free/Net}BSD). Ignores the live process > check for OSes where we don't know how to do this. (I saw no portable way > to do this in stock Python without pulling in other libs). > > -- > > -Todd > > > <2014-05-07_qProcessInfo.diff>_______________________________________________ > > lldb-commits mailing list > > [email protected] > > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits > > -- -Todd
_______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
