https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #17 from Austin English austinenglish@gmail.com --- (In reply to Lunknown from comment #16)
Hello Austin English,
Do you have intructions on doing this?
Cherry pick that commit before building (and revert before running git bisect good/bad or git will complain) to find the other regression.
https://wiki.winehq.org/Reverse_Regression_Testing
has some more info. What you'll want to do is a second bisect, between 1.3.36 and 1.3.37. Your goal is to find the commit that fixes the crash mid/end of level (but before the second crash). So, do:
git bisect start git bisect good wine-1.3.36 # crashes earlier git bisect bad wine-1.3.37 # crashes later ./configure --disable-tests make -j5
then test Rayman. If it crashes loading the second level, consider it bad, if it crashes in first level, it's good.
That will eventually give you some commit, let's call it fixed_sha1.
To then find the original regression, do: git bisect reset git bisect start git bisect good 1.3.22 git bisect bad 1.3.37
as normal. Now, it gets a bit different. For each build, you'll want to do: git show $fixed_sha1 | patch -p1 ./configure --disable tests make -j5 git checkout -f # resets your tree to normal # test rayman here git bisect good/bad # as normal
hope that helps. Ping me on IRC (austin987) if you need more help, or ask on the forums.