One of ASP. NET Debug series: Environment matching

Author: Tess
Link: http://blogs.msdn.com/tess/pages/net-debugging-demos-information-and-setup-instructions.aspx
Wencui http://www.cnblogs.com/David-Qian

Some professional words:

Hang: pending, such as slow program response and long page display time.
Crash: collapsed. For example, w3wp.exe is forced to restart due to a problem.
Memory: memory.
Memory leak: memory leakage, that is, the memory is used too much and is not enough. For example, the exception of OutOfMemoryException occurs.
KB: indicates the Knowledge Base in English. You can view articles in KB from the support site of Microsoft.
Dump: it is equivalent to a memory slice at a static moment.

 

AboutDebugSeries

This is a. net debug series, which includes the most common hang, crash, and memory problems. All the problems will be written in the same website, you can download the http://blogs.msdn.com/tess/attachment/7431454.ashx from here. It is written in ASP. NET and needs to be installed in IIS and. NET Framework 2.0 or later versions. This series will detail some of the important debugging knowledge and help you experience the common problems of debugging.

Install

1) download the sample website. The link is provided above.

2) create a new virtual directory named BuggyBits in IIS.

3) Open http: // localhost/BuggyBits/default.htm and test whether your settings are correct. If you can browse, it indicates that your virtual directory is set 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 in windows from here

6) double-click the InternetConnections. reg file to modify the registry. It is used to increase the number of connections that IE accesses to the same site.

7) install tinyget tool, which is used to stress the test page, so that we can easily reproduce the problems of hang and memory leak. Download In this KB: http://support.microsoft.com/kb/840671

Tool Introduction

• Windbg: it is a tool used to debug the windws program. It is very powerful. By default, it is installed in this directory: c: "program files" debugging tools for windows
• Adplus: This script automatically generates memory dump and stores it in the debuggers directory.
• SOS. dll: An Python extension for debugging hosted (. net) code.
• Tinyget: it is a command line tool that uses the HTTP protocol for multiple threads and loop requests. It has the same functions as the tool used for website stress testing.

Debugger toolsUsage After installation

After Debugger tools is installed, we cannot use windbg immediately. before using it, we need to make the following settings:

1) set.. net directory (for example, C: "Windows" Microsoft.. NET "Framework" v2.0.50727. dll copy to the Debugger directory (C: "Program Files" Debugging Tools for Windows (x86 )).

2) set the symbols of windbg. First, we can create a new folder in the C root directory, such as "c:" symbols "public". This folder will save all symbols downloaded during windbg usage. Open the File menu of windbg, click the symbol file path, and enter "srv * c:" symbols "public * http://msdl.microsoft.com/download/symbols#in the symbol path ".

Now you have set windbg. In the next article, we will explain some windbg commands and make some preparations before debugging.

Have a nice day!