http://bugs.winehq.org/show_bug.cgi?id=23509
--- Comment #3 from Boris bstriker@ya.ru 2010-07-04 17:00:04 --- Bisecting: 77 revisions left to test after this (roughly 6 steps) wine-1.2-rc5-77-g4d9a311 - BAD wine-1.2-rc5-38-g88d1a9b - BAD wine-1.2-rc5-19-gf71c411 - BAD wine-1.2-rc5-9-ga42a091 - BAD wine-1.2-rc5-4-gd97e6a4 - BAD wine-1.2-rc5-2-gfcba272 - BAD wine-1.2-rc5-1-g61a9eef - BAD
61a9eef9a1c0a72e6571742dbb830f7b22c05230 is the first bad commit commit 61a9eef9a1c0a72e6571742dbb830f7b22c05230 Author: Paul Chitescu paulc@voip.null.ro Date: Sat Jun 26 13:24:38 2010 +0300 dbghelp: Provide a non-NULL number of bytes read to ReadProcessMemoryProc64 callback. :040000 040000 b1a4eda8e3442754ad74da959aefa5b11b4473c2 6f83178f5d7ac0ee0c6ae334b2b006f8034383cb M dlls
It's strange, for sure, I did: git reset --hard d474d3f142b6e5f50ca3253cd170695ac3cc8930 wine-1.2-rc5 - BAD!
Obviously, I did something wrong... Should I use the command: CC="ccache gcc" ./configure --verbose && make depend && make after each 'git bisect bad'? Or should I use just 'make'?