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

Re: kernel32/tests: Test deleting a timer right after creating it.

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=15671 Your paranoid android. === W2KPROSP4 (32 bit sync) === sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997 === WXPPROSP3 (32 bit sync) === sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997 === W2K3R2SESP2 (32 bit sync) === sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997 === WVISTAADM (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W2K8SE (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W7PRO (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W7PROX64 (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === TEST64_W7SP1 (32 bit sync) === sync.c:741: Test failed: Timer callback 0 === W7PROX64 (64 bit sync) === sync.c:741: Test failed: Timer callback 0 === TEST64_W7SP1 (64 bit sync) === sync.c:741: Test failed: Timer callback 0

Nov. 28, 2011

Re: [PATCH] dxgi: 0 / 0 means 0 for a DXGI_RATIONAL

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=15670 Your paranoid android. === WVISTAADM (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W2K8SE (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W7PRO (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W7PROX64 (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === TEST64_W7SP1 (32 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. swapchain: unhandled exception c0000005 at 004027AA === W7PROX64 (64 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. Timeout === TEST64_W7SP1 (64 bit swapchain) === swapchain.c:76: Test failed: Failed to create device and swapchain, hr 0x8007000e. Timeout

Nov. 28, 2011

Re: [PATCH 1/5] user32/tests: Initial tests for RawInput functions.

by Vitaliy Margolen

On 11/27/2011 09:10 PM, Marvin wrote: > 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=15663 > > Your paranoid android. > > > === WVISTAADM (32 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 > > === W2K8SE (32 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 > > === W7PRO (32 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 > > === W7PROX64 (32 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 > > === TEST64_W7SP1 (32 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 > > === W7PROX64 (64 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 > > === TEST64_W7SP1 (64 bit input) === > input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 Interesting. This works on Win XP... Will modify the test. BTW anyone can approve my account request to test bot? Vitaliy.

Nov. 28, 2011

Re: [PATCH 5/5] user32: Implement GetRawInputDeviceInfoW completely on user side.

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=15666 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W2K8SE (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PRO (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (32 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (64 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (64 bit input) === input.c:1791: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87

Nov. 28, 2011

Re: [PATCH 3/5] user32: Implement GetRawInputDeviceList completely on user side.

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=15665 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W2K8SE (32 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PRO (32 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (32 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (32 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (64 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (64 bit input) === input.c:1799: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87

Nov. 28, 2011

Re: [PATCH 2/5] user32: Add initial input parameter validations to RawInput functions.

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=15664 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W2K8SE (32 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PRO (32 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (32 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (32 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (64 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (64 bit input) === input.c:1801: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87

Nov. 28, 2011

Re: [PATCH 1/5] user32/tests: Initial tests for RawInput functions.

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=15663 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W2K8SE (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PRO (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (32 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === W7PROX64 (64 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87 === TEST64_W7SP1 (64 bit input) === input.c:1807: Test failed: GetRawInputDeviceInfoA failed: -1, 1024, 87

Nov. 28, 2011

Re: Compiling Wine without prelink

by Roger Cruz

Great. Thanks for the explanation On Nov 27, 2011, at 6:32 PM, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote: > On 11/27/2011 03:24 PM, Roger Cruz wrote: >> Could you expand what exactly would not work? > Some copy-protection systems, and any other programs that do dlls patching using IPC. They assume that some system dlls (namely ntdll, kernel32, and user32) are always loaded to the same address for every system process. > > It was initially added to support SafeDisk copy protection. Now it's hard to tell what other programs might depend on this. > > If you do not have prelink, Wine will not be able to load these DLLs at the same address and some programs will fail in mysterious ways. > > -Vitaliy

Nov. 28, 2011

Re: Compiling Wine without prelink

by Vitaliy Margolen

On 11/27/2011 03:24 PM, Roger Cruz wrote: > Could you expand what exactly would not work? Some copy-protection systems, and any other programs that do dlls patching using IPC. They assume that some system dlls (namely ntdll, kernel32, and user32) are always loaded to the same address for every system process. It was initially added to support SafeDisk copy protection. Now it's hard to tell what other programs might depend on this. If you do not have prelink, Wine will not be able to load these DLLs at the same address and some programs will fail in mysterious ways. -Vitaliy

Nov. 27, 2011

Re: Compiling Wine without prelink

by Roger Cruz

My apologies on mispelling your name Maarten ________________________________ From: Roger Cruz <roger_r_cruz(a)yahoo.com> To: Maarten Lankhorst <m.b.lankhorst(a)gmail.com> Cc: "wine-devel(a)winehq.org" <wine-devel(a)winehq.org> Sent: Sunday, November 27, 2011 5:24 PM Subject: Re: Compiling Wine without prelink Hi Marteen, Could you expand what exactly would not work? Does Wine place the DLLs at a particular address and if not specified with the prelink tool, then they will fail to work? It is my understanding that if the libraries are not prelinked, then the loading linker will pick its own address to load them at. That is the behavior I want to test. My target platform is refusing to map ntdll.dll.so and gives me the following error: "Cannot load library: load_segments[928]: 290 failed to map segment from 'ntdll.dll.so' @ 0xfbe00000 (0x0007b07c). p_vaddr=0x7bc00000 p_offset=0x00000000" I'm looking for a way around this and not p;roviding a base address may do it. Roger ________________________________ From: Maarten Lankhorst <m.b.lankhorst(a)gmail.com> To: Roger Cruz <roger_r_cruz(a)yahoo.com> Cc: "wine-devel(a)winehq.org" <wine-devel(a)winehq.org> Sent: Sunday, November 27, 2011 4:45 PM Subject: Re: Compiling Wine without prelink Hey Roger, On 11/27/2011 10:29 PM, Roger Cruz wrote: > What is the proper way to ask the configure script not to use 'prelink' on the generated shared libraries? I don't want to remove the prelink from my development platform but just tell the configurator to ignore it. > Prelink is only used to force dlls to certain addresses, not for anything else. Without prelink this would not work..

Nov. 27, 2011