How to programmatically detect an application has crashed in Windows?
Question:
I am running a Python script that launches a number of apps. I need a way to detect if the app that’s launched has crashed. Some apps have internal crash handling
How can I detect the crash?
Answers:
If they have internal crash handling, it’s not possible to detect. The application will handle the error and exit normally. You can’t even detect this if you would attach yourself as a debugger.
The reason is exception dispatching (MSDN):
- the debugger gets informed about an exception. This is called the first chance exception. However, this might be “normal”, e.g. FileNotFound, which is expected by the application.
- Windows is looking for someone who wants to handle the exception. This can be the
except block of a Python application, a catch block in C# or C++ or even a general “unhandled exception handler”.
- If nobody wanted to handle the application, the debugger gets informed again. This time, the exception is marked as a second chance exception. This means that the application will crash next.
You’re looking to become informed as part of step 3, however, the application has already stopped the process in step 2.
if the subprocess crashes you should be able to see the dialogue box crash and prompted to take actions either "Debug" or "Close Program".
I am running a Python script that launches a number of apps. I need a way to detect if the app that’s launched has crashed. Some apps have internal crash handling
How can I detect the crash?
If they have internal crash handling, it’s not possible to detect. The application will handle the error and exit normally. You can’t even detect this if you would attach yourself as a debugger.
The reason is exception dispatching (MSDN):
- the debugger gets informed about an exception. This is called the first chance exception. However, this might be “normal”, e.g. FileNotFound, which is expected by the application.
- Windows is looking for someone who wants to handle the exception. This can be the
exceptblock of a Python application, acatchblock in C# or C++ or even a general “unhandled exception handler”. - If nobody wanted to handle the application, the debugger gets informed again. This time, the exception is marked as a second chance exception. This means that the application will crash next.
You’re looking to become informed as part of step 3, however, the application has already stopped the process in step 2.
if the subprocess crashes you should be able to see the dialogue box crash and prompted to take actions either "Debug" or "Close Program".