When looking for the root cause of a crash collecting the memory dump is only the first step. This posting assumes that you already have a properly configured version of WinDBG along with a memory dump of a managed process.
In order to highlight the differences between managed and unmanaged debugging I will continue with the same scenario I used in my unmanaged posting. The following is the scenario we will assume.
You are a software vendor that has written an automated banking machine application. Several times a day the kiosk is restarted by the customer because the application has crashed. In an effort to identify the cause of the crash, which happens when you are not there, you have used ADPLUS to collect a User Mode memory dump. The memory dump has been copied onto your machine and you are ready to start debugging.
To begin debugging open the second chance exception dump by selecting “File -> Open Crash Dump…” and select the dump file to be analyzed. Read more: Practical Development
In order to highlight the differences between managed and unmanaged debugging I will continue with the same scenario I used in my unmanaged posting. The following is the scenario we will assume.
You are a software vendor that has written an automated banking machine application. Several times a day the kiosk is restarted by the customer because the application has crashed. In an effort to identify the cause of the crash, which happens when you are not there, you have used ADPLUS to collect a User Mode memory dump. The memory dump has been copied onto your machine and you are ready to start debugging.
To begin debugging open the second chance exception dump by selecting “File -> Open Crash Dump…” and select the dump file to be analyzed. Read more: Practical Development
Posts
0 comments:
Post a Comment