One of the ASP.net Debug series: Environment matching

Some professional vocabulary:

Hang: hang, such as slow response to the program, long time to display the page and so on.

Crash: Crash, such as W3wp.exe encountered a problem was forced to reboot and so on.

Memory: Memory, this needless to say.

Memory leak: Memory leaks, that is, too much memory use, not enough, such as the occurrence of outofmemoryexception anomalies and so on.

KB: English is the Knowledge base, known as the Knowledgebase, from Microsoft's support site to view the articles in KB.

Dump: A slice that is equivalent to memory at a certain time of rest.

About the Debug series

This is a. NET Debug series, which includes the most common hang,crash and memory issues. All the questions will be written in the same website, and you can download http://blogs.msdn.com/tess/attachment/7431454.ashx from here. It is written in asp.net and needs to be installed on IIS and the. NET Framework 2.0 or later. This series will tell you some important things about debug and let you personally experience how to debug these common problems.

Installation

1 Download sample website, which has been given a link above.

2 Create a new virtual directory in IIS called Buggybits.

3 Open the http://localhost/BuggyBits/default.htm and test whether you set it correctly. If you can browse, it means that your virtual directory is set up correctly.

4 Open http://localhost/BuggyBits/CompanyInformation.aspx to test whether you can browse the ASPX page.

5 Download the debug tools:http://www.microsoft.com/whdc/devtools/debugging/default.mspx under Windows from here

6 double-click the Internetconnections.reg file to modify the registry, which is used to increase the number of connections that IE accesses to the same site.

7 Install Tinyget tool, it is used to stress test page, so we can easily reproduce hang and memory leak problem. There are downloads in this KB: http://support.microsoft.com/kb/840671

Introduction to Tools

WINDBG: It is the Debug WINDWS program a tool, very powerful. By default it is installed in this directory: C: "Program Files" Debugging Tools for Windows

Adplus: This is a script that automatically produces memory dumps and stores them in the debuggers directory.

SOS.dll: Debugging an extension of managed (. NET) code.

Tinyget: It is a command-line tool that uses the HTTP protocol for multithreading (multiple threads), repetitive (loop) request, and Web site stress test tool functionality.

How to use Debugger tools after installation

After installing debugger tools, we can not use WinDbg immediately, before using it to do some of the following settings:

1 SOS.dll Copy to debugger directory under the. NET directory (such as: C: "Windows" Microsoft.NET "Framework" v2.0.50727) (c: "Program Files" debugging Tools for Windows (x86)).

2) Set up the WinDbg symbols. First of all, we can create a new folder in the C-packing directory, such as "C:" Symbols "public", this folder will save all WinDbg use the download symbols. Then open WinDbg's File menu, click Symbol File path and enter "Srv*c:" Symbols "public*http://msdl.microsoft.com/download/symbols" in Symbol path.

Now you've set the WinDbg. In the next article, we'll explain some of WinDbg's commands and do some debug work before we get there.

Have a nice day!

Original Author: Tess

Original link: http://blogs.msdn.com/tess/pages/net-debugging-demos-information-and-setup-instructions.aspx

Translator: Wencui Http://www.cnblogs.com/David-Qian