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

Re: Debugging Wine with Lightroom 3.5

by roland65＠free.fr

Yes, I'm that kind of person (I'm the developer of Xfe and TexMaths) but I've seen the +relay logs logs and they are indeed very huge, even for me! RB ----- Mail original ----- De: "Juan Lang" <juan.lang(a)gmail.com> À: "Roland Baudin" <roland65(a)free.fr> Cc: "Wine Devel" <wine-devel(a)winehq.org> Envoyé: Dimanche 18 Décembre 2011 16:15:49 Objet: Re: Debugging Wine with Lightroom 3.5 Hi Roland, On Sun, Dec 18, 2011 at 6:46 AM, Roland Baudin <roland65(a)free.fr> wrote: > Yes, I suspected such a mechanism. Now if I understand well I have to find > which one is the "builtin mechanism" and which one is the "fallback > mechanism". > Is there some documentation around about the differences between Vista and > XP? That list would be large, too large to be conveniently listed in one place. What one could do, which is unfortunately often equally tedious, is to compare +relay logs from running the app in Wine under both modes. If looking through multi-GB log files is your idea of fun, you have the makings of a Wine developer ;) --Juan

Dec. 20, 2011

Re: [PATCH] comdlg32: Correctly handle filters with multiple file extensions in Save As dialogs (try 2)

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 http://testbot.winehq.org/JobDetails.pl?Key=16065 Your paranoid android. === WVISTAADM (32 bit filedlg) === Timeout === W2K8SE (32 bit filedlg) === Timeout === W7PRO (32 bit filedlg) === filedlg.c:1060: Test failed: TestFilter (*.pt*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.ab?): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.ab?): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: (null): expected TRUE filedlg.c:1066: Test failed: (null): Filename is deadbeef, expected deadbeef.xy* === W7PROX64 (32 bit filedlg) === filedlg.c:1060: Test failed: TestFilter (*.pt*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.ab?): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.ab?): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: (null): expected TRUE filedlg.c:1066: Test failed: (null): Filename is deadbeef, expected deadbeef.xy* === TEST64_W7SP1 (32 bit filedlg) === filedlg.c:1060: Test failed: TestFilter (*.pt*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.ab?): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.ab?): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: (null): expected TRUE filedlg.c:1066: Test failed: (null): Filename is deadbeef, expected deadbeef.xy* === W7PROX64 (64 bit filedlg) === filedlg.c:1060: Test failed: TestFilter (*.pt*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.ab?): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.ab?): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: (null): expected TRUE filedlg.c:1066: Test failed: (null): Filename is deadbeef, expected deadbeef.xy* === TEST64_W7SP1 (64 bit filedlg) === filedlg.c:1060: Test failed: TestFilter (*.pt*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.ab?): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.ab?): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: TestFilter (*.*): expected TRUE filedlg.c:1066: Test failed: TestFilter (*.*): Filename is deadbeef, expected deadbeef.xy* filedlg.c:1060: Test failed: (null): expected TRUE filedlg.c:1066: Test failed: (null): Filename is deadbeef, expected deadbeef.xy*

Dec. 20, 2011

Re: secur32/tests: Fail on missing NTLM

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 http://testbot.winehq.org/JobDetails.pl?Key=16052 Your paranoid android. === WNT4WSSP6 (32 bit ntlm) === ntlm.c:1231: Test failed: AcquireCredentialsHande() returned SEC_E_INVALID_TOKEN ntlm.c:423: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:433: Test failed: expected SEC_E_INTERNAL_ERROR or SEC_I_CONTINUE_NEEDED, got SEC_E_NO_IMPERSONATION ntlm.c:445: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:457: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:885: Test failed: cbSecurityTrailer should be 16 but is 0 ntlm.c:423: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:433: Test failed: expected SEC_E_INTERNAL_ERROR or SEC_I_CONTINUE_NEEDED, got SEC_E_NO_IMPERSONATION ntlm.c:445: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:457: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:885: Test failed: cbSecurityTrailer should be 16 but is 0 ntlm.c:423: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:433: Test failed: expected SEC_E_INTERNAL_ERROR or SEC_I_CONTINUE_NEEDED, got SEC_E_NO_IMPERSONATION ntlm.c:445: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:457: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:885: Test failed: cbSecurityTrailer should be 16 but is 0 ntlm.c:423: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:433: Test failed: expected SEC_E_INTERNAL_ERROR or SEC_I_CONTINUE_NEEDED, got SEC_E_NO_IMPERSONATION ntlm.c:445: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:457: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:885: Test failed: cbSecurityTrailer should be 16 but is 0 ntlm.c:423: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:433: Test failed: expected SEC_E_INTERNAL_ERROR or SEC_I_CONTINUE_NEEDED, got SEC_E_NO_IMPERSONATION ntlm.c:445: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:457: Test failed: expected SEC_E_BUFFER_TOO_SMALL, got SEC_E_INSUFFICIENT_MEMORY ntlm.c:1031: Test failed: MakeSignature returned SEC_E_INVALID_TOKEN, not SEC_E_OK. ntlm.c:1061: Test failed: Crypt trailer not as expected. ntlm.c:1075: Test failed: Crypt message not as expected. ntlm.c:1097: Test failed: DecryptMessage returned SEC_E_MESSAGE_ALTERED, not SEC_E_OK. ntlm.c:1099: Test failed: Failed to decrypt message correctly. ntlm.c:1127: Test failed: MakeSignature returned SEC_E_INVALID_TOKEN, not SEC_E_OK. ntlm.c:1135: Test failed: VerifySignature returned SEC_E_INVALID_TOKEN, not SEC_E_OK ntlm.c:1139: Test failed: EncryptMessage returned SEC_E_INVALID_TOKEN, not SEC_E_OK. ntlm.c:1157: Test failed: Crypt message not as expected. ntlm.c:1176: Test failed: DecryptMessage returned SEC_E_INVALID_TOKEN, not SEC_E_OK.

Dec. 19, 2011

[PATCH 1/4] mmdevapi: Enforce limits on period and duration.

by Joerg-Cyril.Hoehle＠t-systems.com

Hi, the patch catches shared mode very well, however it appears that exclusive mode exhibits vastly different behavior from one machine to the next. As WASAPI is MS' low(est)-level audio API, the observable behavior appears to really depend on the individual HW drivers. Examples: The 8x multiplier is observable with testbot. One particular native w7 native machine (no vmware) does not know that multiplier and is clamping to max 32768 frames instead. That machine seems to use 1024 frames as multiplier for buffer size, i.e. 21.333ms -- which reminds me of ALSA's dmix. Furthermore, its GetCurrentPadding seems to return continuous values. GetPosition follows GCP (like winecoreaudio.drv now does), whereas (several VMs on) testbot exhibit period-sized deltas in GCP -- like in shared mode. IOW, exclusive mode shows quite a range of different behaviours. Wine just has to choose one. Regards, Jörg Höhle

Dec. 19, 2011

Re: [2/2] ws2_32/tests: Add a test to show what happens when the listen socket is closed after an AcceptEx call.

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 http://testbot.winehq.org/JobDetails.pl?Key=16049 Your paranoid android. === W2KPROSP4 (32 bit sock) === sock: unhandled exception c0000005 at 05280023

Dec. 19, 2011

Re: [PATCH 2/6] jscript: Use bytecode for block statement implementation

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 http://testbot.winehq.org/JobDetails.pl?Key=16041 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

Dec. 19, 2011

Re: [PATCH 1/5] ddraw/tests: Introduce some functions for comparing floating-point vectors.

by Henri Verbeet

On 19 December 2011 13:37, Henri Verbeet <hverbeet(a)codeweavers.com> wrote: > + /* The coordinates are all offset by about (1e-6, 1e-6) for some reason. > + * On the y-axis we apparently have somewhat less precision, and the > + * offset gets lost for viewports more than 31 high. */ Except when it doesn't. I'll resend this with a viewport that isn't as sensitive to this.

Dec. 19, 2011

Re: [PATCH 3/5] ddraw/tests: Introduce proper vector types.

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 http://testbot.winehq.org/JobDetails.pl?Key=16036 Your paranoid android. === W2KPROSP4 (32 bit d3d) === d3d.c:559: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W2K3R2SESP2 (32 bit d3d) === d3d.c:559: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W2K8SE (32 bit d3d) === d3d.c:559: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W7PROX64 (32 bit d3d) === d3d.c:559: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === TEST64_W7SP1 (32 bit d3d) === d3d.c:559: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}.

Dec. 19, 2011

Re: [PATCH 2/5] ddraw/tests: Remove a redundant IDirect3DDevice7_SetViewport() call.

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 http://testbot.winehq.org/JobDetails.pl?Key=16035 Your paranoid android. === W2KPROSP4 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W2K3R2SESP2 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W2K8SE (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W7PROX64 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === TEST64_W7SP1 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}.

Dec. 19, 2011

Re: [PATCH 1/5] ddraw/tests: Introduce some functions for comparing floating-point vectors.

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 http://testbot.winehq.org/JobDetails.pl?Key=16034 Your paranoid android. === W2KPROSP4 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W2K3R2SESP2 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W2K8SE (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === W7PROX64 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}. === TEST64_W7SP1 (32 bit d3d) === d3d.c:560: Test failed: Got unexpected vertex 1 {2.55999985e+002, 1.52587891e-005, 9.99999940e-001, 9.99999940e-001}.

Dec. 19, 2011