Shulou(Shulou.com)06/01 Report--

This article shows you what are the methods of .net program debugging and tracking, which are concise and easy to understand, which can definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Preface

As a. Net development engineer, whether writing desktop programs, service programs, or web programs, we must be very familiar with the dynamic debugging skills of vs during the development phase, although web programs may also need to debug front-end scripts or styles, which is beyond the scope of this article. This article mainly introduces the basic knowledge of dynamic debugging of vs and how to track the debug logs or skills of released programs.

Development stage

This stage is mainly based on dynamic debugging, of course, the sharp weapon of debugging is vs.

Dynamic debugging steps:

1. Have the code and pdb file of the program

2. the breakpoint under the line number of the logical code you want to observe

3. Vs- > debug-> start debugging (you may need conditions to trigger the program to execute to the logical line number you want)

4. For running programs, you can also vs- > debug-> attach to a process to complete startup debugging. If the running program is a service process (non-desktop process), check "Show all user processes" in the attach to process dialog box.

Conditional filtering of breakpoints

In dynamic debugging, if a breakpoint is broken in a multithreaded environment, if you use "sentence by sentence" to the next statement, the breakpoint will be broken immediately, making the tracking context very inconvenient; in another case, it is broken in the body of the loop, but only want to track points that meet certain conditions. At these times, you should use a conditional breakpoint, break under a line number of code, and then right-click the left red breakpoint real circle, the pop-up menu can set conditions for the breakpoint, set the breakpoint after the condition, called conditional breakpoint, vs display as a red virtual circle.

Production stage

This stage is mainly tracked, tracking the application log files, debugging information output and exceptions, etc., in the case of not to, you can use remote dynamic debugging to debug.

Log file

You may immediately think of log4net, yes, it can write some debugging information and exception information to a file or db, which is very easy to query. In addition, we should also understand Exceptionless, its power lies in more perfect exception context content collection, exception classification display and summary, viewing exception information in Exceptionless, we can almost statically analyze the cause of the exception and directly modify the code.

Collect debugging information

Due to performance reasons, we usually only record important and abnormal contents in log files, while less important ones generate frequent contents. when we are in the console, we can use Console.WriteXXX to display these contents in real time. In fact, as long as you call the Log method of System.Diagnostics.Debugger, the output of this method can be captured by some tools without debugging. Here are two collection tools provided.

1. Use the DebugViewer tool for collection

This tool is a collector I wrote using. Net. UI is a good friend and has been hosted on github by open source.

2. Use the debugview tool for collection

Collect the contents of Console.WriteXXX

Console.WriteXXX makes it easy to track when writing console programs, but in non-console programs (such as service processes, windows desktop applications, and web applications), these Console.WriteXXX don't actually produce any output. Now our goal is to enable the collection tool to collect this output information in non-console applications as long as Console.WriteXXX is called.

1. When the program is initialized, replace the Out property of the Console static class, Console.SetOut (debugOut)

2. Implement your own DebugOut and output the contents of Write to the Debugger.Log method

Public class DebugOut: System.IO.TextWriter {

Public override void Write (char [] buffer, int index, int count) {var message = new string (buffer, index, count); System.Diagnostics.Debugger.Log (0, null, message);}}

Using this method, I can do a program, when serving as a console, output to control, when running as a service process, the debug information can be received by the collection tool, and our code still calls Console.WriteXXX.

Remote dynamic debugging

It is hoped that the problem can be solved without this step, and the requirement of remote debugging is still relatively high:

1. Remote programs must come with pdb files, preferably exactly the same as the local code.

2. Copy the "remote debugging tool" provided with vs to the remote machine and run the corresponding debugging server according to x86 or x64 system.

3. Vs- > debug-> attach to the process, transfer to "remote (remote without authentication)", and "qualifier" is the ip or domain name of the remote machine.

What are the methods of debugging and tracking .net programs? have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.