Managing a folder with a million files in an ASP application

Lately, I’ve been working on an interesting issue of IIS6 hosting an ASP application where we see that the ASP requests take long time to process requests and ends up hanging the whole worker process.   Well, in such scenarios, the best way to find out the root cause is to take the debugging approach….


High memory utilization in dbghost.exe when using Debugdiag

I have seen lately many issues where Administrators and developers alike are claiming that Debugdiag is causing the whole server to become unresponsive. In some situation, the debugger host (dbghost.exe) grows uncontrollably in memory consumption causing it to shutdown which will bring the target process the debugger was attached to to terminate as well.  In…

1

How to analyze multiple userdumps and generate one report per userdump using Debugdiag 1.1

In many situations, you may find it useful to analyze multiple userdumps at once but generate an analysis report for each userdump analyzed. The Debugdiag UI can still do that, but there is no option now (1.1) to make it generate one analysis report per userdump. If -let’s say- you would like to analyze 10…


Whitepaper on the Debug Diagnostic Tool v1.1

I have recently published a whitepaper on the Debug Diagnostic Tool v1.1 (Debugdiag) at the following location in the download center. The whitepaper gives a detailed description of the tool. It explains the main components of the tool and their usage. It also provides Walkthroughs on how to configure the tool to get the right…

3

Post-mortem Analysis of Userdumps with Debugdiag

This post is an extract of an MSDN whitepaper on debugdiag that will be released soon!   Post-mortem analysis with the windows core debuggers (windbg.exe or cdb.exe) is a time consuming process and requires a lot of debugging skills. Automated post-mortem analysis of usedumps is basically one of the main goals of debugdiag. It is…


Debugging Heap corruption with Application Verifier and Debugdiag

When dynamic allocation/deallocation of memory is not handled properly by user code, this might lead to memory blocks in the heap being corrupted. There are many causes of heap corruption. Some of the common causes are: Buffer overrun (Writing beyond the allocated memory), Double free (Freeing a pointer twice) and Old pointer reuse(Reusing a pointer…

3