Debugging Windows Error Reporting- May 24, 2007 If youre a software developer, chances are that you have written an application, and this application has crashed. When this happened, it probably put up a dialog that looks something like this: How do you figure out what went wrong Strategy 1: Extract the minidump from Windows Error Reporting Windows Error reporting has already created a minidump of the crash. So one way to find out what went wrong is just to look at the minidump. This works really well if your application is written in.http://blogs.msdn.com/greggm/archive/2007/05/24/debugging-windows-error-reporting.aspx Analyzing Tracepoint Output- May 7, 2007 Last week I had this displeasure of tracking down a fairly unpleasant reference counting bug. I wound up having to solve the problem by brute force: Set a breakpoint in the constructor of leaking object Set a data breakpoint on the object's reference count variable Change the data breakpoint to a tracepoint that prints the callstack (see dialog) Match up the callstacks. However, my tracepoint was hit so often that matching up callstacks by hand proved to be impossible. To help, I...http://blogs.msdn.com/greggm/archive/2007/05/07/analyzing-tracepoint-output.aspx |