Basic approach
(This article is reproduced from Software Engineering Expert Network
Www.21cmm.com)
The missed (ie debug) is accompanied by successful test shadows. The symbol of the test success is discovered. Determine the cause and accurate position of the error based on the error signs, and correctly rely mainly on the wrong technology. 1. The troubleshooting process is as shown in the figure below, the tap process begins with the execution of a test case. If the test results are entry and the expected result, the error sign has occurred, and the error process first analyzes the error, and then corrects the error. Therefore, there are two possibilities, one is to find the cause of the error and correct the error, the other may be unknown, and the tired person has to do some speculation, and then design the test case to confirm this speculation, if once The estimation failed, then the second speculation until the error was found and corrected. Drawing is a fairly tough process. In addition to developers' psychological obstacles, it is also because the mistakes hidden in the program have the following special nature: (1) Error's external signs away from internal causes of errors, for Highly coupled program structure This phenomenon is more serious; (2) Correct a mistake caused another error (temporary) disappearance; (3) Some error signs is just illusion; (4) Because the operator is negligent Some error signs are not easy to track; (5) errors are due to the wind rather than the program; (6) Input conditions are difficult to accurately construct (for example, the input order of some real-time applications is uncertain); (7) Error indicating Sometimes there is no, this phenomenon is particularly common to the embedded system; (8) errors are caused by the distribution of tasks in several different processing machines. During the software troubleshooting process, you may have a large and small, have a problem, with the increase in the problem, the pressure of the tattoo person is also increased, which is too nervous to cause the developer to exclude a problem while introducing more New problems. Although it is not a good way to learn (sometimes people are more willing to call it art), there are still a variety of effective methods and strategies, and the following describes several tired methods. 2. The tired method does not use which tired method, the target is only one, ie, the cause of the income is discovered, which requires a good combination of intuitive imagination and system assessment. Commonly used troubleshooting strategies are divided into three categories: 1 BRUTE force 2 Trace (Cause Eliminations) The original class tired method is the most commonly used method, only in the unavailable situation Use it under, the main idea is "Find the error". For example, the content of the output memory, the register, and the program arranges several output statements, etc., with a large number of field information, from which the wrong clues are found, although it can be successful, it is inevitable to consume a lot of time and energy. The backtrackwork can be successfully used for the troubleshooting of the program. The method is to start from the error symbol, and the artificial edge of the control process is tracked back until the root cause of the error is found. Unfortunately, the program has increased, and the possible backtrack route has increased significantly, so that it is not possible to completely retro it.
