On Wed, 21 Mar 2001 00:07:16 +0800, you wrote:
> Hello all.
>
> I have this very strange situation:
> Debugging with +relay,+win,+region,+message has revealed:
> ...
> Call user32.18: CallNextHookEx(4b483218,00000000,00000001,405a3f40) ret=3d1010fe
>fs=008f
> Ret user32.18: CallNextHookEx() retval=00000000 ret=3d1010fe fs=008f
> trace:message:SPY_EnterMessage (0000565c) {Static} message
>[0087]
> WM_GETDLGCODE sent from self wp=00000000 lp=00000000
> trace:relay:WINPROC_CallWndProc
> (wndproc=0x40619540,hwnd=0000565c,msg=WM_GETDLGCODE,wp=00000000,lp=00000000)
> trace:relay:WINPROC_CallWndProc
> (wndproc=0x40619540,hwnd=0000565c,msg=WM_GETDLGCODE,wp=00000000,lp=00000000)
>retval=00000100
> trace:message:SPY_ExitMessage (0000565c) {Static} message
>[0087]
> WM_GETDLGCODE returned 00000100
> wine: debugtools.c:210: wine_dbg_vprintf: Assertion `ret < sizeof(info->output) -
>(info->out_pos -
> info->output)' failed.
> err:ntdll:RtlpWaitForCriticalSection Critical section 0x40685190 wait timed out,
>retrying (60 sec)
> fs=0287
>
> It seemed to be as libc bug and I have upgraded my stock rh 6.2 from
> ftp://updates.redhat.com/6.2 to the latest available glibc-2.1.3-22.i386.rpm
> and glibc-devel-2.1.3-22.i386.rpm. But nothing has changed.
>
Yes, when I saw this, I just increased the string sizes of the
debug_info structure in the top of debugtools.c.
Those sizes seem to be quite calculated, but I haven't realy looked
yet how this calculation is done and why it is wrong.
Rein.
--
Rein Klazes
[EMAIL PROTECTED]