[lldb-dev] crashed vs. stopped process state

[Greg Clayton]

On Dec 13, 2012, at 11:22 AM, "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote:

> 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?

eStateCrashed means a non-recoverable stop state where the process can't continue and must be terminated. If we know the test is causing a crash state, then we should inforce this and fix the Mac side to comply and return the correct state.

I would be interested to know what these cases are where the Mac is not returning the crashed state.

Greg


> Thanks,
> Andy
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev