Windgb,sos,adplus,tinyget Common Commands

In the previous translation, we mainly explained the debug series of Tess and the installation and setup of debugger tools. Before translating the next article, I would like to explain some common commands of windbg,sos,adplus and Tinyget. After you have understood these, you will be able to understand the later articles more easily.

One of the ASP.net Debug series: Environment matching

1.adplus

This scripting tool was installed with debugger tools. can automatically help you monitor a program, and under the conditions you set to generate a dump file saved in the debugger directory. When using these tools, you need to cut the command prompt window to the debugger directory. Common usage is as follows:

Adplus-hang-pnw3wp.exe

When the dump is generated in the hang state, ADPlus immediately produces the dump file. After you enter this command and press ENTER, the command will immediately get a w3wp.exe memory slice. But this command will pop up a confirmation window, and if you find this more cumbersome, you can add the –quiet command at the end to avoid pop-up windows.

Adplus-hang-p1234–quiet

I believe you will soon find that the uplink command is the process name used, and this command is the process ID used. At the same time, it can generate dump directly, does not eject the confirmation window.

Adplus-crash-pnw3wp.exe

This command is the dump when you get the program crash. Unlike hang, which immediately gets the dump, it will always attach on the W3wp.exe program until the W3wp.exe program crash. Other similar parameters have the same effect.

Of course, if you use Vista, you can easily get the dump file in Task Manager by right-clicking Create dump files.

2. Tinyget

This tool is used to stress test a website. The most common commands are:

Tinyget-srv:localhost-uri:/buggybits/featuredproducts.aspx-threads:30-loop:50

This command indicates that 30 threads are also started to send 50 requests to the Featuredproducts page of the Buggybits site on local IIS. You can also use the "Tinyget/?" in the Command window. See more detailed commands.

3. WinDbg

WinDbg's orders are a bit of a number (.) To start, it is different from the start of the exclamation Mark command (!), the beginning of the exclamation mark command is sos.dll in the command.

. Load SOS

Each time you open WinDbg to debug the dump of the. NET program, we first enter this command. Its purpose is to enable WinDbg to support the debugging of managed (managed code).

. Time

View the time when the dump file was generated, including the current time of the system, total boot time, total running time of the program, total time of the program running in kernel state and total user state.