[lldb-dev] crashed vs. stopped process state

[Kaylor, Andrew]

There are a couple of tests that are failing on Linux because the test is intentionally crashing the inferior process and expecting the process state to be eStateStopped, whereas on Linux the actual process state in these situations is eStateCrashed.  I understand that on Darwin the state is eStateStopped in these cases, though I don't know why.

Can anyone shed some light on this for me?

Thanks,
Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20121213/8789b187/attachment.html>