This tutorial demonstrates launching the sample application, crashing the application and using Bug Validator to identify the location and cause of the crash. The tutorial is performed without MFC code instrumented, so that MFC message processing and pointer validation calls are not part of the application trace.
Scroll to the bottom of the display. The image will look similar to the image shown below.
The exception caused by the crash is caught in the unhandled exception filter (shown above). Scroll upwards in the list looking for the start of the message processing that caused the crash. The image below shows the call that started the message processing. This is in the CCrashEditBox::OnLButtonDblClick() method.
This tutorial demonstrated a more complex crash than the simple crash. As you can see, interpreting the trace data is not always trivial, some detective work is required to correctly identify the cause of the problem.
Future versions of Bug Validator will provide: