[Bug 14598] New: eStateCrashed should be removed as a process state


             Bug #: 14598
           Summary: eStateCrashed should be removed as a process state
           Product: lldb
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
        AssignedTo: lldb-dev@cs.uiuc.edu
        ReportedBy: andrew.kaylor@intel.com
    Classification: Unclassified

When the inferior process crashes, the process state should be eStateStopped
with stop info used to describe the crashed state. The eStateCrashed state
should be removed.

Via e-mail from Greg Clayton:

After speaking with Jim Ingham, we came up with:

- eStateCrashed should be removed all together, anywhere that was using this
should be changed to eStateStopped
- The thread stop info is where the info should be contained for crashes
- In the future, we should add a StopClass enumeration that has accessors on
the thread stop info class where the enum is something like:

enum StopClass
   eStopClassNormal, // Normal expected stop (used for breakpoints,
watchpoints, etc)
   eStopClassCrash, // Program will likely crash if there are no handlers
   eStopClassFatalCrash // This will always crash the program };