Post Production Debugging for ASP.NET Applications – Part 1
page 5 of 7
by Rahul Soni
Feedback
Average Rating: 
Views (Total / Last 10 Days): 32652/ 48

Debugging Tool for windows

In my opinion, this tool is The One which gives you answers when Debug Diagnostic tool fails. The downside is that this tool has a very steep learning curve and the GUI is not one for the faint hearted. I do not want to scare you by saying all this, but unfortunately this is true. Debugging a memory dump using WinDBG is difficult, but there are a lot of experts doing just that at Microsoft and have a great level of expertise in analyzing the dump files and troubleshooting IIS/ASP.NET and all sorts of other issues. If you see that you have already collected a set of dumps along with the Perfmon data you can call Microsoft and ask them to help you troubleshoot your issue.

Microsoft help and support
Support Options from Microsoft Services

In case you are of a curious type, I would suggest just 3 links which can help you. http://mtaulty.com/communityserver/blogs/mike_taultys_blog/archive/2004/08/03/4656.aspx
http://www.codeproject.com/debug/windbg_part1.asp
http://blogs.msdn.com/dougste/articles/clrdebug.aspx

In the forthcoming articles, I will discuss more about WinDBG and some very specific issues which come up.


View Entire Article

User Comments

Title: Thanks!   
Name: Guy
Date: 2007-07-31 5:02:49 AM
Comment:
Great article, some extremely useful stuff. Thanks :-)

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2024 ASPAlliance.com  |  Page Processed at 2024-03-29 2:54:44 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search