http://bugs.winehq.org/show_bug.cgi?id=15928
--- Comment #5 from Daniele nekrosius@alice.it 2008-11-13 10:16:26 --- (In reply to comment #4)
Regression testing revealed the bad commit to be:
72a3f1833873cc0e84c4b6639eaf13e6a4ec497c is first bad commit commit 72a3f1833873cc0e84c4b6639eaf13e6a4ec497c Author: James Hawkins truiken@gmail.com Date: Sun Sep 16 18:30:20 2007 -0500
kernel32: Return TRUE for all pointer params in GlobalUnlock.
:040000 040000 060db0975218ee4dbb4788117a2e131593e5d469 1c8099a4359777e7c20446ef9cb15ce176625ed7 M dlls
Although I was not able to automatically revert the commit, building from the commit before that makes the problem disappear.
Thank you for doing regression test, I also tried but I was not able to identify the bad commit. Now that you know what is the bad commit, what can I do to be able to use again EasyPlot with wine...?