On Fri, 2004-08-27 at 21:04, Bryce Harrington wrote:
We also need to have people test each of the nightly builds, going back in time until we find the first Win32 CVS version that crashes, so we can do a diff to find out which changes went into that version.
For those of you following along at home, a binary search is probably the best way of going about this; find two builds that are reasonably far apart, where the oldest one doesn't fail, but the newest one does. The offending changes are somewhere in-between.
Next, try a build halfway in-between the first two you checked; if it fails, then the breakage happened somewhere in the first half, otherwise someplace in the second. Repeat the process within that smaller interval, and so forth... eventually it'll be narrowed down to one day.
-mental