On 4/12/06, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> "Jesse Allen" <[EMAIL PROTECTED]> writes:
>
> > WaitForSingleObject in kernel32. The read call is in wait_reply of
> > dlls/ntdll/thread.c and that is where that thread gets stuck.
>
> Does this help?
>
> diff --git a/server/window.c b/ser
On 4/11/06, Fabian Cenedese <[EMAIL PROTECTED]> wrote:
>
> >Ok, I'm not sure about it waiting for that event. The call is
> >0009:Call kernel32.WaitForSingleObject(0048,) ret=00401c00
> >
> >Anyway I wrote a test app, showwindow.c. It is available on
> >ftp://resnet.dnip.net . The rela
"Jesse Allen" <[EMAIL PROTECTED]> writes:
> WaitForSingleObject in kernel32. The read call is in wait_reply of
> dlls/ntdll/thread.c and that is where that thread gets stuck.
Does this help?
diff --git a/server/window.c b/server/window.c
index 8254793..5ceab49 100644
--- a/server/window.c
+++ b/
>>Anyway I wrote a test app, showwindow.c. It is available on
>>ftp://resnet.dnip.net . The relay log is there too. The test app tries
>>to mimic the calls I see. I tested under wine and it does hang. I
>>will see about windows.
>
>I don't know if I did it right. I created an empty Win32 applica
>Ok, I'm not sure about it waiting for that event. The call is
>0009:Call kernel32.WaitForSingleObject(0048,) ret=00401c00
>
>Anyway I wrote a test app, showwindow.c. It is available on
>ftp://resnet.dnip.net . The relay log is there too. The test app tries
>to mimic the calls I see.
On 4/11/06, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> "Jesse Allen" <[EMAIL PROTECTED]> writes:
>
> > Start of process 0x8:
> >
> > Creates 16x16 window, WS_POPUP style in thread 0x9, 10024 (Root Window)
> > ShowWindow 10024
> > In ShowWindow set_active_window
> > Creates a new thread 0x
On 4/11/06, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> "Jesse Allen" <[EMAIL PROTECTED]> writes:
>
> > Start of process 0x8:
> >
> > Creates 16x16 window, WS_POPUP style in thread 0x9, 10024 (Root Window)
> > ShowWindow 10024
> > In ShowWindow set_active_window
> > Creates a new thread 0x
"Jesse Allen" <[EMAIL PROTECTED]> writes:
> Start of process 0x8:
>
> Creates 16x16 window, WS_POPUP style in thread 0x9, 10024 (Root Window)
> ShowWindow 10024
> In ShowWindow set_active_window
> Creates a new thread 0xc
> Starts process 0xe
> CreateEvent "WARCRAFT_III_OK" and waits on read
On 4/10/06, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Jesse Allen <[EMAIL PROTECTED]> writes:
>
> > There is a problem with explorer managing the desktop and the sending of
> > PAINT messages. I've narrowed it down to the following area. In
> > dlls/user/message.c wait_message_reply(), if QS_
Jesse Allen <[EMAIL PROTECTED]> writes:
> There is a problem with explorer managing the desktop and the sending of
> PAINT messages. I've narrowed it down to the following area. In
> dlls/user/message.c wait_message_reply(), if QS_PAINT are the bits we get,
> and we call MsgWaitForMultipleObjects
Hi,
There is a problem with explorer managing the desktop and the sending of
PAINT messages. I've narrowed it down to the following area. In
dlls/user/message.c wait_message_reply(), if QS_PAINT are the bits we get,
and we call MsgWaitForMultipleObjectsEx, it seems to block the process
indefinite
11 matches
Mail list logo
