http://bugs.winehq.org/show_bug.cgi?id=7448
------- Additional Comments From focht@gmx.net 2007-19-02 06:48 ------- Thanks, but nothing new revealed...
--- snip --- =>1 0x7d28dc7b (0x0034f7e8) 0016:trace:ole:DllMain 0x7e980000 0x3 (nil) 2 0x7ee7c123 call_window_proc+0xca(hwnd=0x1002c, msg=0xf, wp=0x0, lp=0x0, result=0x34fdcc, arg=0x7d28dc7b) [/home/jisakiel/wine-0.9.31/dlls/user32/winproc.c:452] in user32 (0x0034f838) --- snip ---
From what i've seen the windowproc pointer points to possible heap area
(0x7d28dc7b) which seems invalid - hence the access violation. I remember some rare occurrences where WindowProc() might get called with dangling pointer. For instance when bugged code uses class libraries (like ATL, MFC and the like) incorrectly by deleting window objects (like CWnd...) before calling DestroyWindow(). There are cases where even class libraries contain such bugs (like the dreaded "delete this" in OnFinalMessage() )
I would test this app using native windows. Wine isnt useful in this case.
Please run the software using "Windows Application Verifier" (http://www.microsoft.com/technet/prodtechnol/windows/appcompatibility/appver...) tool. Here is a little "howto": http://msdn2.microsoft.com/en-us/library/ms807121.aspx
If the software is bugged, the tool should report heap issues ("Page Heap") prior to crash.
Report back if you encounter any problems or have new info.
-
Wine Bugs