[Lldb-commits] [lldb] r199290 - Fix a bug where if we stop but nobody says there was a reason for the stop, we would return

Ed Maste emaste at freebsd.org
Fri Jan 17 07:35:30 PST 2014


 On 14 January 2014 22:32, Jim Ingham <jingham at apple.com> wrote:
> Author: jingham
> Date: Tue Jan 14 21:32:42 2014
> New Revision: 199290
>
> URL: http://llvm.org/viewvc/llvm-project?rev=199290&view=rev
> Log:
> Fix a bug where if we stop but nobody says there was a reason for the stop, we would return
> control to the user anyway.

After this change LLDB fails for me on FreeBSD:

joule% bin/lldb /usr/bin/true
Current executable set to '/usr/bin/true' (x86_64).
(lldb) run
error: initial process state wasn't stopped: exited

Is the first stop ID not 1 (instead of 0)?  That's what I see on
FreeBSD and in my Debian VM.  My guess is that we have the issue you
describe in the commit message and I'll investigate, but changing the
test to "GetStopID() > 1" restores the existing behaviour for me.



More information about the lldb-commits mailing list