Debugger: Remove the InferiorExited state
There are now several possible orders of events between sending a 'kill'
and receiving something that indicated a properly shut down inferior.
Coordinating the InferiorExited state during engine ramp down is not
worthwhile as that state had only a forced transition to InferiorShutdownOk
anyway. For the user (and user code), only the fact that ramp down is
finished is interesting.
Change-Id: Ic22131d5a1066dc62bd069f532c28b773f231088
Reviewed-by:
Christian Stenger <christian.stenger@theqtcompany.com>
Showing
- src/plugins/debugger/debuggerconstants.h 0 additions, 2 deletionssrc/plugins/debugger/debuggerconstants.h
- src/plugins/debugger/debuggerengine.cpp 3 additions, 10 deletionssrc/plugins/debugger/debuggerengine.cpp
- src/plugins/debugger/debuggerplugin.cpp 1 addition, 1 deletionsrc/plugins/debugger/debuggerplugin.cpp
- src/plugins/debugger/gdb/gdbengine.cpp 5 additions, 3 deletionssrc/plugins/debugger/gdb/gdbengine.cpp
- src/plugins/debugger/qml/qmlcppengine.cpp 0 additions, 6 deletionssrc/plugins/debugger/qml/qmlcppengine.cpp
Loading
Please register or sign in to comment