[darcs-users] Delta Debugging

Tanksley, William D. Jr. WILLIAM.D.TANKSLEY.JR at saic.com
Mon May 24 16:11:04 UTC 2004

From: Samuel A. Falvo II

>On Sunday 23 May 2004 09:44 pm, Kenneth Knowles wrote:
>> For those who don't have time to read the papers, the idea is that 
>> starting with the last known working configuration of a program, you 
>> apply the changes gradually until it breaks.  The algorithm is more 
>> sophisticated, and finds a minimal set of changes causing the error. 
>> It is parameterized by the type of "change" you are applying and the 
>> test function.  In the papers, the examples are very impressive, 
>> narrowing bugs in GCC, GDB, and Mozilla down to a couple 
>> lines out of thousands, or even characters.

>It sounds to me that if one follows the process of test-driven 
>development, this whole thing becomes unnecessary.  Am I missing 

I think so. TDD doesn't promise that you'll not get bugs; and when you get
them, it would be very nice to have a way to narrow them down automatically.
TDD'ed code would be much easier to narrow things down to.

>Samuel A. Falvo II


More information about the darcs-users mailing list