http://bugs.winehq.org/show_bug.cgi?id=22629
--- Comment #21 from Wylda wylda@volny.cz 2010-05-14 02:32:36 --- (In reply to comment #20)
"This should give you yours segfault: git checkout -f 246f9305e9f8eb18e54018746143d95afed887be compile wine & test your game (should segfault)"
this does not segfault :-( Fu.k ....
i really should redo the Regression Testing
Hmmm... that mean you slip somewhere with good/bad marking.
But it also mean, that commit 246f9305e9f8eb18e54018746143d95afed887be is good. Then narrow the commit space. So instead of doing:
git bisect reset git bisect start git bisect good wine-1.1.37 git bisect bad wine-1.1.38
do:
git bisect reset git bisect start git bisect good 246f9305e9f8eb18e54018746143d95afed887be git bisect bad wine-1.1.38
And you hopefully save time and few compile rounds.