ASP.NET Tips: How to capture a dump

DotNetKicks.com — Sun, 06 Apr 2008 17:45:27 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: ASP.NET Tips: How to capture a dump

molotov — Sun, 06 Apr 2008 20:04:55 GMT

Pre-Vista systems also have Dr. Watson:

drwtsn32.exe -p <pid>

Of course, this has the nasty side-effect of terminating the target process... ;-)

re: ASP.NET Tips: How to capture a dump

Tom — Mon, 07 Apr 2008 02:57:03 GMT

Very true. It just is easier in the newer versions since you can do it directly from Task Manager. There are many other ways to collect a dump, like using windbg for example.

re: ASP.NET Tips: How to capture a dump

molotov — Mon, 07 Apr 2008 03:07:55 GMT

> There are many other ways to collect a dump, like using windbg for example. <

Sure. In earlier OS's, drwtsn32.exe is about the only thing that came with the OS (that I am aware of) that could get you a dump, without already having additional software installed or installing it and then hoping to recreate the problem. And, if a customer won't let you install any software on their systems (but is OK with you taking down the process :-O )...

So, it is indeed a good thing that it is easier to capture dumps with in-built tools...

re: ASP.NET Tips: How to capture a dump

Tom — Mon, 07 Apr 2008 05:08:06 GMT

The other great thing is WER. Since it can upload the dump to Microsoft and we can analyze it to see if it is a known issue. If it is, we can refer you to the fix right away.

It is also a great way to let Microsoft know about any problems you are experiencing in our software.

re: ASP.NET Tips: How to capture a dump

Josh Coswell — Tue, 08 Apr 2008 00:22:11 GMT

This is more insightful then I used to think about exceptions.

Josh Coswell

http://riverasp.net