https://bugs.winehq.org/show_bug.cgi?id=41002
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |christopherwuy@gmail.com
--- Comment #12 from fjfrackiewicz@gmail.com ---
(In reply to Matteo Bruni from comment #9)
(In reply to fjfrackiewicz from comment #8)
I read up on regression testing, tried a few of the commands in there as far as bisecting goes but it looks like it requires knowledge of the components the bisection command lists in order to flag them as either a good or bad commit.
Actually it doesn't. You just need to compile Wine at each step, test Worms and then run "git bisect good" if Worms works fine or "git bisect bad" if it fails with the error in this bug.
You need to be able to compile Wine to do a bisection, obviously. You also need a starting point, that's why you should look for a Wine version that works first. According to comment 6, 1.8.3 should work so you should probably try with 1.8 (1.8.3 and 1.9.15 are on two separate branches so bisecting between them is a bit trickier than necessary).
Well, I got a seemingly "bad" commit when using these commands at the start of the bisection:
git bisect start git bisect good wine-1.8 git bisect bad wine-1.9.0
and then "git bisect bad" every time the game crashed with the Visual C++ error
The commit in question:
2ed5d0afc1e516c65a2f606ead009e666ffc29ff is the first bad commit commit 2ed5d0afc1e516c65a2f606ead009e666ffc29ff Author: YongHao Hu christopherwuy@gmail.com Date: Mon Dec 21 12:15:34 2015 +0800
msvcp110: Add tr2_sys__Read_dir implementation.
Signed-off-by: YongHao Hu christopherwuy@gmail.com Signed-off-by: Piotr Caban piotr@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
I am really unsure of this but that's what I got. If someone smarter than me can point me in a different direction I need to take in order to check this, please feel free to do so.