|
From: Johannes S. <Joh...@gm...> - 2005-01-20 14:17:51
|
Hi, I once had the same problem as you: I updated from a CVS project, and the program broke. As it was a year since I had updated, I decided to do a binary search through the patches, but soon found out that I am not good enough in book-keeping. So I wrote the attached shell script. You just call it from the root directory of valgrind, and it asks a few questions, then tries to check out a version "in the middle between known good and known bad" until it can compile cleanly. It then exits and asks you to run a test. Then you call it again and tell it if the version is good or bad, and the script again tries to check out a middle version, and so on. Eventually it will pin down the patch (or a set of patches if compilation fails between those patches) which broke the feature you need. Maybe you find this useful... Ciao, Dscho |