Wine segfaulting

[gerard patel]

On Wed, 5 Dec 2001 19:59:21 +0100, Pavel Troller <patrol at sinus.cz>
wrote:
<snip>
>0806ea10:Call x11drv.SetWindowText(00010029,403f8c18 L"&Ok") ret=406efe21
>0806ea10:Ret  x11drv.SetWindowText() retval=00000001 ret=406efe21
>0806ea10:Ret  window proc 0x406c1dbc (hwnd=00010029,msg=WM_NCCREATE,wp=00000000,lp=404d4554) retval=00000001
>0806ea10:Call window proc 0x406c1dbc (hwnd=00010029,msg=WM_NCCALCSIZE,wp=00000000,lp=404d41d8)
>0806ea10:Ret  window proc 0x406c1dbc (hwnd=00010029,msg=WM_NCCALCSIZE,wp=00000000,lp=404d41d8) retval=00000300
>0806ea10:Call window proc 0x406c1dbc (hwnd=00010029,msg=WM_CREATE,wp=00000000,lp=404d4554)
>0806ea10:Call x11drv.LoadOEMResource(00007ff7,00000001) ret=406eddb2
>Segmentation fault
>
>When I added +file,+dosfs, there was no difference in this part, so I think there are
>no file operations involved.
>
>Please note that although there were many window operations before the crash,
>there was no window visible on the screen.
>
>I don't have any idea what does OEM Resource mean. Could it be that my wine installation is broken ?
<snip>

Possibly this has nothing to do with the immediate line preceding
the segfault. It could be a recursive call exhausting the program's
stack. Check if there is a pattern of repetition before.

Gerard