April 2016 - Wine-Devel - list.winehq.org

Re: Fix a heap corruption when printing specific REG_MULTI_SZ values.

by Hugh McMaster

On Saturday, 23 April 2016 3:35 AM, Sebastian Lackner wrote: >The current calculation does not take the terminating \0 into account. > -buffer = HeapAlloc(GetProcessHeap(), 0, tmp_size * 2); > +buffer = HeapAlloc(GetProcessHeap(), 0, tmp_size * 2 + sizeof(WCHAR)); Which particular cases cause the heap corruption? -- Hugh McMaster

April 23, 2016

Re: Wine inside Xephyr on OSX

by Bruno Jesus

On Sat, Apr 23, 2016 at 11:43 AM, Henri Verbeet <hverbeet(a)gmail.com> wrote: > On 23 April 2016 at 11:15, Bruno Jesus <00cpxxx(a)gmail.com> wrote: >> Now I was trying to do the same in an OSX, so I have opened Xephyr and >> DISPLAY=:2 xeyes work but Wine windows are not created inside the >> Xephyr window as if the DISPLAY is completely ignored. Is there any >> way to make this work? >> > You don't mention how you're invoking things exactly, but my first > thought would be to make sure you're using winex11 and not winemac. Sorry, it was: Xephyr :2 -screen 640x480x24 DISPLAY=:2 xeyes & DISPLAY=:2 wine winecfg And right, since I don't use OSX I completely forgot about winemac. I just read Useful Registry Keys page and switched to X11, but now wine does not load at all: err:x11drv:process_attach failed to load libX11.6.dylib: dlopen(libX11.6.dylib, 266): image not found err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly. This is without setting DISPLAY. Clearly it is a missing dependency that I have to install, but the main issue was this x11/winemac difference, thanks.

April 23, 2016

Re: Wine inside Xephyr on OSX

by Henri Verbeet

On 23 April 2016 at 11:15, Bruno Jesus <00cpxxx(a)gmail.com> wrote: > Now I was trying to do the same in an OSX, so I have opened Xephyr and > DISPLAY=:2 xeyes work but Wine windows are not created inside the > Xephyr window as if the DISPLAY is completely ignored. Is there any > way to make this work? > You don't mention how you're invoking things exactly, but my first thought would be to make sure you're using winex11 and not winemac.

April 23, 2016

Wine inside Xephyr on OSX

by Bruno Jesus

Hi, all. In Debian I have been using Xephyr to test some applications when virtual desktop is not enough, so far so good. Now I was trying to do the same in an OSX, so I have opened Xephyr and DISPLAY=:2 xeyes work but Wine windows are not created inside the Xephyr window as if the DISPLAY is completely ignored. Is there any way to make this work? Best wishes, Bruno

April 23, 2016

Re: [PATCH] d3dx10: Implement D3DX10UnsetAllDeviceObjects()

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=22481 Your paranoid android. === build (build) === Make failed

April 23, 2016

Re: [PATCH 6/8] ddraw: Return early in d3d_device7_DrawIndexedPrimitiveVB() with a 0 vertex or index count.

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=22465 Your paranoid android. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

April 22, 2016

Re: [PATCH 5/8] ddraw: Return early in d3d_device7_DrawPrimitive() with a 0 vertex count.

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=22464 Your paranoid android. === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

April 22, 2016

Re: [PATCH 4/8] ddraw: Return early in d3d_device7_DrawPrimitiveStrided() with a 0 vertex count.

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=22463 Your paranoid android. === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

April 22, 2016

Re: [PATCH 3/8] ddraw: Return early in d3d_device7_DrawIndexedPrimitive() with a 0 vertex or index count.

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=22462 Your paranoid android. === w1064 (32 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

April 22, 2016

Re: [PATCH 2/8] ddraw: Return early in d3d_device7_DrawIndexedPrimitiveStrided() with a 0 vertex or index count.

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=22461 Your paranoid android. === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

April 22, 2016