http://bugs.winehq.org/show_bug.cgi?id=29949
--- Comment #8 from Robert Riches rmriches@ieee.org 2012-02-20 12:41:45 CST --- Ran the regression again from the start. This is what I got from the regression run this time:
8e1dbebdb0e7b834fad53b4ea3d3cd349c34fbec is the first bad commit commit 8e1dbebdb0e7b834fad53b4ea3d3cd349c34fbec Author: Alexandre Julliard julliard@winehq.org Date: Mon Feb 13 12:28:32 2012 +0100
hhctrl.ocx: Fix a buffer allocation size.
:040000 040000 9c3402bf12e5f8ae6b2524be350a5307b8adabf3 6f075ef166278ca3c7e9e5daa7b93cf536771fd6 M dlls
However, reverting that patch did not fix the symptoms. The symptoms do change a little from run to run, even with the same compiled code; namely, sometimes it's an unhandled page fault that crashes WINE, and sometimes WINE just hangs.
The somewhat non-deterministic symptoms and such are causing me to suspect a memory allocation or reference issue of the type Valgrind is made to solve. Is WINE normally Valgrind-clean? Would it make sense to try using Valgrind to find this thing?