漂亮的调试.pptx

漂亮的调试Delta DebuggingAutomated debugging approach based on scientific methodFind failure-inducing circumstances automatically circumstances such as the program input, changes to the program code, or program executions.The Scientific Method of DebuggingObserve some aspect of the universeInvent a tentative description, called a hypothesis, that is consistent with the observationUse the hypothesis to make predictionsTest those predictions by experiments or further observations and modify the hypothesis in the light of your results.Repeat steps 3 and 4 until there are no discrepancies between hypothesis and experiment and/or observation.The Scientific Method of Debugging(2)Narrowing down the circumstances of a failureFailure-inducing circumstancesA True StoryDate: Fri, 31 Jul 1998 15:11:05 -0500From: Brian Kahne mailto:bkahne@bkahne@To: DDD Bug Report Address mailto:ddd-bugs@ips.cs.tu-bs.deddd-bugs@ips.cs.tu-bs.deSubject: Problem with DDD and GDB 4.17When using DDD with GDB 4.16, the run command correctly uses any prior command-line arguments, or the value of “set args”. However, when I switched to GDB 4.17, this no longer worked: If I entered a run command in the console window, the prior command-line options would be lost. […]Delta debuggingYesterday, my program worked. Today, it does not. Why?Assumption: The failure is caused by one of the changes between yesterday and todayGoal: Finding and examine this failure-inducing change.Procedure: Delta DebuggingA Simple ApproachSystematic testing can narrow down the change set automatically - for instance by divide and conquer along the revision history:Complexity O(logn): 1024 changes = 10 test runsA single logical change can affect thousands of lines of code – but only a few lines may be responsible for the failure.TroubleThere can be multiple failure-inducing changes that cause the failure only when applied together.Combinations of changes that don’t result in a testable program.Narrowing Down the set of changesAssumption