- wine-devel - winehq.org

Re: riched20: fix memory leak
by Alexandre Julliard 07 Dec '11

07 Dec '11

Pierre Schweitzer <pierre(a)reactos.org> writes: > @@ -102,6 +102,7 @@ ME_UndoItem *ME_AddUndoItem(ME_TextEditor *editor, ME_DIType type, const ME_Disp > } > default: > assert(0 == "AddUndoItem, unsupported item type"); > + ME_DestroyDisplayItem(pItem); > return NULL; It's not useful to free memory in unreachable code paths. -- Alexandre Julliard julliard(a)winehq.org

1 0

dosdevices/c not present.. how is it created?
by Roger Cruz 07 Dec '11

07 Dec '11

I'm getting the following error when running Wine. err:process:init_windows_dirs directory L"C:\\windows" could not be created, error 2 err:process:init_windows_dirs directory L"C:\\windows\\system32" could not be created, error 3 Using the debugger, I think I found where the problem is: 2140 int fd = open( unix_name, O_RDONLY | O_DIRECTORY ); (gdb) p unix_name $25 = 0x4040b2e8 "/data/winehome/dosdevices/c:" (gdb) n 2141 if (fd != -1) (gdb) p fd $26 = -1 (gdb) where #0 find_file_in_dir (unix_name=0x4040b2e8 "/data/winehome/dosdevices/c:", pos=29, name=0x4040b2c6, length=7, check_case=0, is_win_dir=0x0) at /home/rcruz/sandbox/wine-dev-branch/dlls/ntdll/directory.c:2141 #1 0x80236cf4 in lookup_unix_name (name=0x4040b2c6, name_len=0, buffer=0xbebc45e4, unix_len=295, pos=28, disposition=2, check_case=0 '\0') at /home/rcruz/sandbox/wine-dev-branch/dlls/ntdll/directory.c:2759 #2 0x80237ad4 in wine_nt_to_unix_file_name (nameW=0xbebc48f8, unix_name_ret=0xbebc4844, disposition=2, check_case=0 '\0') at /home/rcruz/sandbox/wine-dev-branch/dlls/ntdll/directory.c:2981 #3 0x80237004 in nt_to_unix_file_name_attr (attr=0xbebc4900, unix_name_ret=0xbebc4844, disposition=2) at /home/rcruz/sandbox/wine-dev-branch/dlls/ntdll/directory.c:2821 #4 0x8023b744 in FILE_CreateFile (handle=0xbebc48ec, access=2147483648, attr=0xbebc4900, io=0xbebc48f0, alloc_size=0x0, attributes=128, sharing=1, disposition=2, options=33, ea_buffer=0x0, ea_length=0) at /home/rcruz/sandbox/wine-dev-branch/dlls/ntdll/file.c:125 #5 0x8023bd40 in NtCreateFile (handle=0xbebc48ec, access=2147483648, attr=0xbebc4900, io=0xbebc48f0, alloc_size=0x0, attributes=128, sharing=1, disposition=2, options=33, ea_buffer=0x0, ea_length=0) at /home/rcruz/sandbox/wine-dev-branch/dlls/ntdll/file.c:271 #6 0x8045d210 in ?? () export WINEPREFIX=/data/winehome When I look in my $WINEPREFIX directory, I can see that the c: directory is not there # ls /data/winehome system.reg dosdevices drive_c user.reg # ls /data/winehome/dosdevices # How does that c: directory get created and by whom? I have deleted the $WINEPREFIX several times already to no avail. Thanks Roger R. Cruz # ls /data/winehome system.reg dosdevices drive_c user.reg # ls /data/winehome/dosdevices #

2 2

Re: cmd: Use FormatMessage() for better internationalization support.
by Frédéric Delanoy 06 Dec '11

06 Dec '11

On Tue, Dec 6, 2011 at 17:40, Francois Gouget <fgouget(a)free.fr> wrote: > This makes it possible to reorder the format string placeholders in message translations. > Also add a WCMD_format_string() function to mirror the WCMD_output*() ones and so all resources can use the same formatting style. > This also simplifies the padding code for the 'dir /w' command. > + static const WCHAR empty[] = {'\0'}; There's already a suitable nullW string available

1 0

Re: [2/2] msi/tests: Try harder to remove a shortcut file.
by Marvin 06 Dec '11

06 Dec '11

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=15780 Your paranoid android. === WNT4WSSP6 (32 bit install) === install.c:5994: Test failed: Per-user icon file isn't where it's expected (C:\WINNT\Profiles\Default User\Application Data\Microsoft\Installer\{7DF88A49-996F-4EC8-A022-BF956F9B2CBB}\testicon)

1 0

Re: [PATCH 1/7] msvcrt: Added _get_current_locale impementation
by Piotr Caban 06 Dec '11

06 Dec '11

This patches are broken, please ignore them. I'll need to implement locale reference counters inside msvcrt first.

1 0

Updated Clang static analysis results / Valgrind update
by Austin English 05 Dec '11

05 Dec '11

Web space usage was getting a bit high, so I've uploaded a tarball to a file download service: http://www.sendspace.com/file/5hot36 austin@aw21 ~ $ sha1sum scan-build-2011-07-02.tar.bz2 ac3cb3920ef97641fff1f5376f8136cef01f15bf scan-build-2011-07-02.tar.bz2 to use, just extract and open in your favorite browser: $ firefox index.html this was run against Clang from svn: clang version 3.0 (trunk 134320) Please send me any false positives that you'd like me to report upstream. Cheers, Austin P.S. For those of you wanting Valgrind results, I'm currently hitting a nasty Valgrind bug, waiting on upstream to fix: https://bugs.kde.org/show_bug.cgi?id=275673 (Thanks to Andrew N for finding the faulty commit)

4 7

Re: wined3d: recognize Nvidia 540M
by Henri Verbeet 05 Dec '11

05 Dec '11

On 5 December 2011 21:43, Austin English <austinenglish(a)gmail.com> wrote: > {"GTS 450", CARD_NVIDIA_GEFORCE_GTS450}, /* Geforce 400 - midend low */ > + {"GT 540M", CARD_NVIDIA_GEFORCE_GT540M}, /* Geforce 500 - midend mobile */ > {"GT 440", CARD_NVIDIA_GEFORCE_GT440}, /* Geforce 400 - lowend */ The tables are sorted roughly by generation.

1 0

Re: [PATCH] gdi32: Check get_dc_ptr result (Coverity)
by Alexandre Julliard 05 Dec '11

05 Dec '11

Marcus Meissner <meissner(a)suse.de> writes: > Checked 199 out of 204 times, so do it here too. > CID 5484 It cannot fail inside driver functions. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 4/6] jscript: Use bytecode for invalid assignments
by Marvin 05 Dec '11

05 Dec '11

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=15759 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

1 0

Re: [PATCH 1/6] jscript: Use bytecode for assignment to identifier
by Marvin 05 Dec '11

05 Dec '11

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=15758 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

1 0

Re: [PATCH 3/3] ddraw/tests: Update a copyright line
by Marvin 04 Dec '11

04 Dec '11

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=15757 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: dinput: Clarify a translatable string
by Vitaliy Margolen 04 Dec '11

04 Dec '11

On 12/04/2011 01:33 AM, Frédéric Delanoy wrote: > me> Could you explain what that "Sort Assigned" means? > author> I was planning on sorting the button/action mappings putting the > ones which already have an assigned mapping first, and then all the > others. > --- > + AUTOCHECKBOX "Sort Assigned Mappings", IDC_CHECKBOXSORT, 120, 215, 90, 8 A better way of saying this would be "Show assigned first". Vitaliy.

3 3

Re: user32: Avoid crashing if we can't alloc text buffer
by Nikolay Sivov 03 Dec '11

03 Dec '11

On 12/3/2011 04:35, Bruno Jesus wrote: > If LocalLock fails the buffer is not allocated and get_text_length, which is used in several different places, will make wine crash. LocalLock doesn't allocate anything. You need to figure out why buffer is not allocated at this point.

2 1

Re: [PATCH] dsound: Validate format in primary buffer's SetFormat()
by Marvin 02 Dec '11

02 Dec '11

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=15748 Your paranoid android. === WVISTAADM (32 bit dsound) === Failure running script in VM: The specified guest user must be logged in interactively to perform this operation

1 0

Re: [PATCH 1/3] ddraw: Size handling fixes for IDirect3DDevice::GetCaps (try 4)
by Alexandre Julliard 02 Dec '11

02 Dec '11

stefan(a)codeweavers.com writes: > +static inline BOOL check_d3ddevicedesc_size(DWORD size) > +{ > + if (size == 172 || size == 204 || size == sizeof(D3DDEVICEDESC) /* 252 */) return TRUE; > + return FALSE; > +} You should use something like FIELD_OFFSET instead of these magic constants. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: cmd: Print error messages on stderr, not on stdout. (try3)
by Frédéric Delanoy 02 Dec '11

02 Dec '11

On Fri, Dec 2, 2011 at 10:07, Francois Gouget <fgouget(a)free.fr> wrote: > --- > > I meant to resend this one as [2/2] in my previous series but forgot. > With the resynchronization points we can now handle the fixed output > correctly in the tests this time. > > programs/cmd/builtins.c | 20 ++++++++++---------- > programs/cmd/tests/test_builtins.cmd | 1 - > programs/cmd/tests/test_builtins.cmd.exp | 7 +++---- > 3 files changed, 13 insertions(+), 15 deletions(-) Hi François. Would you mind updating the http://wiki.winehq.org/CmdConformanceTests page with your synchronization stuff? I'm not quite sure what/how it does exactly. There is now a discrepancy between wine output, and testrunner output, e.g. echo ------ eol option for /f "eol=@" %%i in (" ad") do echo %%i echo bar gave ------ eol option Syntax error bar but not gives ------ eol option bar Shouldn't cmd output always give the same as test runner output (which is supposed to run cmd on the input file (test_builtins.cmd), albeit with some preprocessing)? Frédéric

2 5

Re: [PATCH 3/3] user32: If a dialog has no tab-accessible controls, set focus to first control (with tests)
by Marvin 02 Dec '11

02 Dec '11

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=15740 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/2] winecfg: Bump NT 3.51 to Service Pack 5
by Vitaliy Margolen 02 Dec '11

02 Dec '11

On 12/01/2011 12:15 PM, André Hentschel wrote: > --- > - { "nt351", "Windows NT 3.5", 3, 51, 0x421, VER_PLATFORM_WIN32_NT, "Service Pack 2", 0, 0, "WinNT"}, > + { "nt351", "Windows NT 3.51", 3, 51, 0x421, VER_PLATFORM_WIN32_NT, "Service Pack 5", 5, 0, "WinNT"}, You need to do the same in ntdll/version.c Vitaliy.

1 0

Re: shell32/tests: Initialize all fields of SHFILEOPSTRUCT variables (Coverity)
by Marvin 02 Dec '11

02 Dec '11

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=15738 Your paranoid android. === WNT4WSSP6 (32 bit shlfileop) === shlfileop.c:1011: Test failed: Expected aborted operations shlfileop.c:2214: Test failed: SHGetNewLinkInfoA succeeded

1 0

Re: [PATCH 3/3] ddraw/tests: Add a IDirect3DDevice7 GetCaps test
by Marvin 01 Dec '11

01 Dec '11

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=15731 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [PATCH 3/3] ddraw/tests: Add a IDirect3DDevice7 GetCaps test
by Marvin 01 Dec '11

01 Dec '11

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=15731 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/2] kernel32: Add a bunch of VirtualProtect tests on a memory-mapped file. Resend.
by Alexandre Julliard 01 Dec '11

01 Dec '11

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > --- > dlls/kernel32/tests/virtual.c | 187 +++++++++++++++++++++++++++++++++------- > 1 files changed, 154 insertions(+), 33 deletions(-) That's a good start, but it would be interesting to try this with various combinations of CreateFileMapping/MapViewOfFile protections, as I expect that the mapping protections would influence what you can then do in VirtualProtect. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [PATCH 3/3] ddraw/tests: Add a IDirect3DDevice2 GetCaps test
by Henri Verbeet 01 Dec '11

01 Dec '11

On 1 December 2011 11:57, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > An IDirect3DDevice3 test will follow once the d3d initialization design has > been approved. > If we're going to redo the way the tests work anyway, we probably shouldn't reuse the same objects for everything either.

2 1

Re: [PATCH 1/3] ddraw: Size handling fixes for IDirect3DDevice::GetDesc (try 3)
by Henri Verbeet 01 Dec '11

01 Dec '11

On 1 December 2011 11:51, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > Subject: [PATCH 1/3] ddraw: Size handling fixes for IDirect3DDevice::GetDesc There is no IDirect3DDevice::GetDesc(). > + if(size == 172 || size == 204 || size == sizeof(D3DDEVICEDESC) /* 252 */) return TRUE; Please fix the formatting here as well.

1 0

Re: [PATCH 2/3] ddraw/tests: Add a IDirect3DDevice7 GetCaps test
by Marvin 01 Dec '11

01 Dec '11

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=15726 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

2 1

Re: [PATCH 3/3] ddraw/tests: Add a IDirect3DDevice2 GetCaps test
by Marvin 01 Dec '11

01 Dec '11

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=15727 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

difficulties compiling or installing git on precise pagolin
by Susan Cragin 01 Dec '11

01 Dec '11

In the development version of ubuntu, wine can neither be compiled nor installed. ~$ sudo apt-get build-dep wine1.3 [sudo] password for susan: Reading package lists... Done Building dependency tree Reading state information... Done The following packages have unmet dependencies: ia32-libs : Depends: ia32-libs-multiarch libsane-dev : Depends: libjpeg-dev Depends: libtiff4-dev but it is not going to be installed E: Build-dependencies for wine1.3 could not be satisfied. $ sudo apt-get install wine1.3 The following packages have unmet dependencies: wine1.3 : Depends: ia32-libs (>= 1.6) but it is not going to be installed ia32-libs is now a transitional package. There is no ia32-libs-multiarch. It has been replaced by ia32-libs-multiarch:386. It seems as if the problem can first be solved by installing ia32-libs-multiarch:386, but when I try to do this it involves removing other packages that seem important. ??

2 1

Re: [3/3] ddraw/tests: Add a IDirect3DDevice2 GetCaps test
by Marvin 01 Dec '11

01 Dec '11

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=15723 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/3] ddraw/tests: Add a IDirect3DDevice7 GetCaps test
by Marvin 01 Dec '11

01 Dec '11

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=15722 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: Patch for #29144
by Henri Verbeet 01 Dec '11

01 Dec '11

2011/12/1 Aurélien COUDERC <zecoucou(a)free.fr>: > @@ -5189,7 +5189,7 @@ static void fillGLAttribFuncs(const struct wined3d_gl_info *gl_info) > multi_texcoord_funcs[WINED3D_FFP_EMIT_USHORT4N] = invalid_texcoord_func; > multi_texcoord_funcs[WINED3D_FFP_EMIT_UDEC3] = invalid_texcoord_func; > multi_texcoord_funcs[WINED3D_FFP_EMIT_DEC3N] = invalid_texcoord_func; > - if (gl_info->supported[NV_HALF_FLOAT]) > + if (gl_info->supported[NV_VERTEX_PROGRAM] && gl_info->supported[NV_HALF_FLOAT]) > { > /* Not supported by ARB_HALF_FLOAT_VERTEX, so check for NV_HALF_FLOAT */ > multi_texcoord_funcs[WINED3D_FFP_EMIT_FLOAT16_2] = (glMultiTexCoordFunc)GL_EXTCALL(glMultiTexCoord2hvNV); I missed this the first time, but this one shouldn't depend on NV_VERTEX_PROGRAM, only the functions for specifying vertex attributes do.

1 0

Re: Patch for #29144
by Frédéric Delanoy 01 Dec '11

01 Dec '11

2011/12/1 Aurélien COUDERC <zecoucou(a)free.fr>: > Please find an attached patch for #29144. > > It probably fixes a hole range of freezes with fglrx (Tested on Sykrim and > Might & Magic Heroes VI for instance). Please follow WineHQ Patch submission guidelines as described on http://wiki.winehq.org/SubmittingPatches

1 0

Re: [PATCH 2/6] appwiz.cpl: Add Catalan translation
by André Hentschel 30 Nov '11

30 Nov '11

Am 30.11.2011 08:39, schrieb Alex Henrie: > --- > dlls/appwiz.cpl/Ca.rc | 85 +++++++++++++++++++++++++++++++++++++++++++ > dlls/appwiz.cpl/Makefile.in | 1 + > 2 files changed, 86 insertions(+), 0 deletions(-) > create mode 100644 dlls/appwiz.cpl/Ca.rc > > diff --git a/dlls/appwiz.cpl/Ca.rc b/dlls/appwiz.cpl/Ca.rc > new file mode 100644 > index 0000000..e411bf0 > --- /dev/null > +++ b/dlls/appwiz.cpl/Ca.rc > @@ -0,0 +1,85 @@ > +/* > +* Add/Remove Programs English resources > +* > +* Copyright 2001-2002, 2008 Owen Rudge > +* Copyright 2005-2006 Jacek Caban really? :) -- Best Regards, André Hentschel

1 0

Re: [PATCH 1/5] wined3d: Don't apply fixups to converted surfaces.
by Stefan Dösinger 30 Nov '11

30 Nov '11

Am Donnerstag, 24. November 2011, 22:52:32 schrieb Henri Verbeet: > + if (surface->flags & SFLAG_CONVERTED) > + { > + ENTER_GL(); > + glEnable(textype); > + checkGLcall("glEnable(textype)"); > + LEAVE_GL(); > + return WINED3D_OK; > + } I don't think this is correct. E.g. signed formats without GL_NV_texture_shader have load time and read time fixups and both have to be applied. What exactly are you trying to fix? I assume it is something about P8 blits, but P8->P8 blits don't enter the ARB blitting code(due to the dest fixup check), and I don't know of any app that uses P8->RGB or SNORM->UNORM blits. Stefan

3 16

Re: [PATCH 3/5] ddraw: Keep the primary surface mapped at the same address for early ddraw versions.
by Stefan Dösinger 30 Nov '11

30 Nov '11

Am Mittwoch, 30. November 2011, 06:01:46 schrieb Henri Verbeet: > + if (flags & WINED3D_SURFACE_PIN_SYSMEM) > + surface->flags |= SFLAG_PIN_SYSMEM; The address will still change when GetDC is called. Is this intentional? > + /* Some applications assume that the primary surface will always be > + * mapped at the same address. Some of those also assume that this > + * address is valid even when the surface isn't mapped, and that > + * updates done this way will be visible on the screen. The game Nox > + * is such an application. */ I've seen ddraw applications that create systemmem primaries, and we currently allow this. What surface caps does Nox use? Does Nox expect us to magically pick up the new data, or does it map and unmap the surface to get the data onto the screen?

1 0

Re: [PATCH 2/4] jscript: Use bytecode for delete on array expression implementation
by Marvin 30 Nov '11

30 Nov '11

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=15711 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

1 0

Re: [PATCH 1/5] ddraw: Resize the swapchain window on mode changes in exclusive mode.
by Marvin 30 Nov '11

30 Nov '11

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=15710 Your paranoid android. === WVISTAADM (32 bit d3d) === Failure running script in VM: The specified guest user must be logged in interactively to perform this operation

2 1

Re: [PATCH 5/5] user32: Implement GetRawInputDeviceInfoW completely on user side. (resend)
by Marvin 29 Nov '11

29 Nov '11

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=15692 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W2K8SE (32 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PRO (32 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (32 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (32 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (64 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (64 bit input) === input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

1 0

Re: [PATCH 3/5] user32: Implement GetRawInputDeviceList completely on user side. (resend)
by Marvin 29 Nov '11

29 Nov '11

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=15691 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W2K8SE (32 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PRO (32 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (32 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (32 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (64 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (64 bit input) === input.c:1794: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

1 0

Re: [PATCH 2/5] user32: Add initial input parameter validations to RawInput functions. (resend)
by Marvin 29 Nov '11

29 Nov '11

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=15690 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W2K8SE (32 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PRO (32 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (32 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (32 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (64 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (64 bit input) === input.c:1797: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

1 0

Re: [PATCH 1/5] user32/tests: Initial tests for RawInput functions. (try 2)
by Marvin 29 Nov '11

29 Nov '11

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=15689 Your paranoid android. === WVISTAADM (32 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W2K8SE (32 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PRO (32 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (32 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (32 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === W7PROX64 (64 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737 === TEST64_W7SP1 (64 bit input) === input.c:1803: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

1 0

Re: user32: Fix 64-bit 'msg' test hang in test_timers (try 2).
by Dmitry Timoshkov 28 Nov '11

28 Nov '11

"Erich E. Hoover" <ehoover(a)mines.edu> wrote: > The attached patch changes the test_timers() crash function to use > RtlRaiseException (if available) rather than attempting to write to memory > address 0. This change stops the timer tests from hanging on the 64-bit VM. Why not use kernel32.RaiseException (which is always available) instead? -- Dmitry.

2 4

Re: [1/2] kernel32: Add a test for protections accepted by CreateFileMapping, make it pass under Wine.
by Alexandre Julliard 28 Nov '11

28 Nov '11

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > @@ -350,9 +350,6 @@ HANDLE WINAPI CreateFileMappingW( HANDLE hFile, LPSECURITY_ATTRIBUTES sa, > > switch(protect) > { > - case 0: > - protect = PAGE_READONLY; /* Win9x compatibility */ > - /* fall through */ Did you try your test on Win9x? -- Alexandre Julliard julliard(a)winehq.org

3 6

Re: [3/5] cmd/tests: Tweak subsection headers so they are treated as resynchronization points.
by Marvin 28 Nov '11

28 Nov '11

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=15676 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [2/5] cmd/tests: Standardize the batch file section headers.
by Marvin 28 Nov '11

28 Nov '11

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=15675 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: kernel32/tests: Test deleting a timer right after creating it.
by Marvin 28 Nov '11

28 Nov '11

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

1 0

Re: [PATCH] dxgi: 0 / 0 means 0 for a DXGI_RATIONAL
by Marvin 28 Nov '11

28 Nov '11

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

1 0

Re: [PATCH 1/5] user32/tests: Initial tests for RawInput functions.
by Marvin 28 Nov '11

28 Nov '11

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

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel