December 2014 - Wine-Devel - list.winehq.org

Re: [PATCH 8/8] wined3d: Pass WM_SYSCOMMAND(SC_RESTORE) to DefWindowProc.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10609 Your paranoid android. === w8 (32 bit device) === device.c:1222: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1267: Test failed: Reset failed, hr 0x88760868. device.c:1269: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1273: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1280: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1281: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1282: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1283: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1284: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1285: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1290: Test failed: Screen width is 640, expected 800. device.c:1291: Test failed: Screen height is 480, expected 600. device.c:1297: Test failed: Back buffer width is 640, expected 800. device.c:1299: Test failed: Back buffer height is 480, expected 600. device.c:1329: Test failed: Screen width is 640, expected 1024. device.c:1330: Test failed: Screen height is 480, expected 768. device.c:2550: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2555: Test failed: The focus window is active. device.c:2563: Test failed: Got unexpected hr 0x88760869. device.c:2569: Test failed: Got unexpect screen size 800x600. device.c:2584: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2593: Test failed: Got unexpect screen size 800x600. device.c:2606: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2614: Test failed: Got unexpect width 640. device.c:2615: Test failed: Got unexpect height 480.

Dec. 4, 2014

Re: [PATCH 7/8] wined3d: Filter messages generated by focus handling.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10607 Your paranoid android. === w8 (32 bit device) === device.c:1222: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1267: Test failed: Reset failed, hr 0x88760868. device.c:1269: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1273: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1280: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1281: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1282: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1283: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1284: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1285: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1290: Test failed: Screen width is 640, expected 800. device.c:1291: Test failed: Screen height is 480, expected 600. device.c:1297: Test failed: Back buffer width is 640, expected 800. device.c:1299: Test failed: Back buffer height is 480, expected 600. device.c:1329: Test failed: Screen width is 640, expected 1024. device.c:1330: Test failed: Screen height is 480, expected 768. device.c:2550: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2555: Test failed: The focus window is active. device.c:2563: Test failed: Got unexpected hr 0x88760869. device.c:2569: Test failed: Got unexpect screen size 800x600. device.c:2584: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2593: Test failed: Got unexpect screen size 800x600. device.c:2606: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2614: Test failed: Got unexpect width 640. device.c:2615: Test failed: Got unexpect height 480.

Dec. 4, 2014

Re: [PATCH 6/8] ddraw/tests: Test WM_SYSCOMMAND handling.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10606 Your paranoid android. === w8 (32 bit ddraw2) === ddraw2.c:3814: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. === w8 (32 bit ddraw4) === ddraw4.c:4169: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.

Dec. 4, 2014

Re: ole32: fixed CoWaitForMultipleHandles cause app hang

by Changhui Liu

Hi, it's not your recent fix cause. The app is named QQ, a very popular IM client in China. When it runs, it create two process named QQ.exe and TXPlatform.exe. The TXPlatform.exe is an out-of-process COM server, The QQ.exe is the GUI process. When the user click the exit button of the QQ.exe, the QQ.exe and TXPlatform.exe both hang. The backtrace of the GUI thread of QQ.exe is like this: =>0 0xf779d42e __kernel_vsyscall+0xe() in [vdso].so (0x0033e938) 1 0xf7598e1b __libc_read+0x4a() in libpthread.so.0 (0x0033e938) 2 0x7ef8ec9a wait_select_reply+0x30(cookie=0x33e968) 3 0x7ef8fac6 server_select+0x20c(select_op=0x33ea8c, size=0x8, flags=0x2, timeout=(nil)) 4 0x7ef998e7 NtWaitForMultipleObjects+0xbc(count=0x1, handles=0x33ebe0, wait_any=1, alertable=0, timeout=(nil)) 5 0x7ecbcd31 WaitForMultipleObjectsEx+0x191 in kernel32 (0x0033ecf8) 6 0x7e13c224 CoWaitForMultipleHandles+0x4e2 in ole32 (0x0033edf8) 7 0x7e1775b8 ClientRpcChannelBuffer_SendReceive+0x598 in ole32 (0x0033eef8) ... And the backtrace of another thread of QQ.exe is like this: Backtracing for thread 0080 in process 003c (C:\Program Files\Tencent\QQ\Bin\QQ.exe): Backtrace: =>0 0xf779d42e __kernel_vsyscall+0xe() in [vdso].so (0x020ce2a8) 1 0xf7598e1b __libc_read+0x4a() in libpthread.so.0 (0x020ce2a8) 2 0x7ef8ec9a wait_select_reply+0x30(cookie=0x20ce2d8) 3 0x7ef8fac6 server_select+0x20c(select_op=0x20ce3fc, size=0x8, flags=0x2, timeout=(nil)) 4 0x7ef998e7 NtWaitForMultipleObjects+0xbc(count=0x1, handles=0x20ce550, wait_any=1, alertable=0, timeout=(nil)) 5 0x7ecbcd31 WaitForMultipleObjectsEx+0x191 6 0x7ecbcae7 WaitForSingleObject+0x45 7 0x7e179258 dispatch_rpc+0x350(msg=0x3f24668) in ole32 (0x020ce788) 8 0x7e0c10fa process_request_packet+0x3b8(conn=0x158370, hdr=0x55a12e8, msg=0x3f24668) in rpcrt4 (0x020ce8c8) 9 0x7e0c15c6 RPCRT4_process_packet+0x114(conn=0x158370, hdr=0x55a12e8, msg=0x3f24668, auth_data=0x0(nil), auth_length=0) in rpcrt4 (0x020ce928) 10 0x7e0c1759 RPCRT4_worker_thread+0x4e( in rpcrt4 (0x020ce978) ... The dispatch_rpc thread has post a 0x400 RPC message to the GUI thread and is waiting for GUI thread to process the RPC request. But the GUI thread has received WM_QUIT message, the message_loop variable set to FALSE and it only wait for event signal, so the 0x400 RPC message can't be handled. The TXPlatform.exe hang because it is waiting for dispatch_rpc thread send RPC result to a named pipe. Because the hang is too complex , I don't know how to add a test for it. ------------------ Original ------------------ From: "Sebastian Lackner"<sebastian(a)fds-team.de>; Date: Wed, Dec 3, 2014 06:42 PM To: "liuchanghui"<liuchanghui(a)linuxdeepin.com>; Cc: "wine-devel"<wine-devel(a)winehq.org>; Subject: Re: ole32: fixed CoWaitForMultipleHandles cause app hang On 03.12.2014 08:15, Changhui Liu wrote: > > > Do I understand you correctly that this is caused by my recent fix of CoWaitForMultipleHandles? Which app is it? Your change might be correct, but to ensure that this is the case please add a test for it: http://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ole32/tests/compobj.c… Moreover you should completely remove old code then, not just comment it out. Regards, Sebastian

Dec. 4, 2014

Re: [PATCH 5/8] d3d8/tests: Test WM_SYSCOMMAND handling.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10605 Your paranoid android. === w8 (32 bit device) === device.c:1222: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1267: Test failed: Reset failed, hr 0x88760868. device.c:1269: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1273: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1280: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1281: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1282: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1283: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1284: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1285: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1290: Test failed: Screen width is 640, expected 800. device.c:1291: Test failed: Screen height is 480, expected 600. device.c:1297: Test failed: Back buffer width is 640, expected 800. device.c:1299: Test failed: Back buffer height is 480, expected 600. device.c:1329: Test failed: Screen width is 640, expected 1024. device.c:1330: Test failed: Screen height is 480, expected 768. device.c:2550: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2555: Test failed: The focus window is active. device.c:2563: Test failed: Got unexpected hr 0x88760869. device.c:2569: Test failed: Got unexpect screen size 800x600. device.c:2584: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2593: Test failed: Got unexpect screen size 800x600. device.c:2606: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2614: Test failed: Got unexpect width 640. device.c:2615: Test failed: Got unexpect height 480.

Dec. 4, 2014

Re: [PATCH 3/8] d3d8/tests: Test focus loss message filtering.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10603 Your paranoid android. === w8 (32 bit device) === device.c:1222: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1267: Test failed: Reset failed, hr 0x88760868. device.c:1269: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1273: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1280: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1281: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1282: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1283: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1284: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1285: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1290: Test failed: Screen width is 640, expected 800. device.c:1291: Test failed: Screen height is 480, expected 600. device.c:1297: Test failed: Back buffer width is 640, expected 800. device.c:1299: Test failed: Back buffer height is 480, expected 600. device.c:1329: Test failed: Screen width is 640, expected 1024. device.c:1330: Test failed: Screen height is 480, expected 768. device.c:2524: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2529: Test failed: The focus window is active. device.c:2537: Test failed: Got unexpected hr 0x88760869. device.c:2543: Test failed: Got unexpect screen size 800x600. device.c:2558: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2567: Test failed: Got unexpect screen size 800x600. device.c:2580: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2587: Test failed: Got unexpect width 640. device.c:2588: Test failed: Got unexpect height 480.

Dec. 4, 2014

Re: urlmon/tests: Remove unused strings (Clang)

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10595 Your paranoid android. === w2008s64 (32 bit url) === url.c:1478: Test failed: progress 2: hres = 1, expected 0 url.c:1668: Test failed: unexpected call OnProgress_FINDINGRESOURCE url.c:1478: Test failed: progress 1: hres = 1, expected 0 url.c:1680: Test failed: unexpected call OnProgress_CONNECTING url.c:1478: Test failed: progress 2: hres = 1, expected 0 url.c:1701: Test failed: unexpected call OnProgress_SENDINGREQUEST

Dec. 4, 2014

Re: user32/tests: Remove unused variables (Clang)

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10592 Your paranoid android. === w7u (32 bit msg) === msg.c:12105: Test failed: unexpected hwnd 0012013C msg.c:12127: Test failed: bad time 310a2/310b2

Dec. 4, 2014

Re: user32/tests: Remove unused variables (Clang)

by André Hentschel

Am 03.12.2014 um 23:53 schrieb André Hentschel: > --- > dlls/user32/tests/msg.c | 112 ------------------------------------------------ > 1 file changed, 112 deletions(-) Just want to note, that this code was added in 2003 and most likely has never been used, just in case someone wonders why i dare to remove so much code ;)

Dec. 3, 2014

Re: [PATCH 08/15] msvcr120: Remove stray parameter specs for stub functions.

by Martin Storsjö

> Martin Storsjö <martin(a)martin.st> writes: > > > Ok, thanks for clarifying. The issue I encountered was that if I ran > > tools/make_specfiles afterwards (after setting up msvcr120_app to be > > synced against msvcr120), the make_specfiles script ended up changing > > msvcr120_app.spec like this: > > > > -@ stub _wperror > > +@ cdecl _wperror(wstr) msvcr120._wperror > > > > (Which is wrong since _wperror only is a stub in msvcr120 as well.) > > There's nothing wrong with forwarding to a stub. Oh, of course. Then there's no issue at all, and this patch can be dropped. // Martin

Dec. 3, 2014