Ok, I'm not sure about it waiting for that event. The call is 0009:Call kernel32.WaitForSingleObject(00000048,ffffffff) 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. 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 application with VC6, added your file, added an #include <stdio.h> for printf and compiled it successfully. Upon running a window shortly flashes up and the program ends, but no messages are printed to the command window.
Most important thing I guess is that it didn't hang.
bye Fabi
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 application with VC6, added your file, added an #include <stdio.h> for printf and compiled it successfully. Upon running a window shortly flashes up and the program ends, but no messages are printed to the command window.
Most important thing I guess is that it didn't hang.
Forgot to add: That's on Windows 2000 Pro SP2.
bye Fabi
On 4/11/06, Fabian Cenedese Cenedese@indel.ch wrote:
Ok, I'm not sure about it waiting for that event. The call is 0009:Call kernel32.WaitForSingleObject(00000048,ffffffff) 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. 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 application with VC6, added your file, added an #include <stdio.h> for printf and compiled it successfully. Upon running a window shortly flashes up and the program ends, but no messages are printed to the command window.
Most important thing I guess is that it didn't hang.
Yes, it is ok. I guess windows' default printf output is something equivelent to /dev/null. Just redirect it to a file and you'll see it. Try it on wine and you'll see the hang.