May 2012 - Wine-Devel - list.winehq.org

Re: [PATCH] devenum: Do not fail with a IBindCtx (with tests)
by Dmitry Timoshkov May 16, 2012

May 16, 2012

Detlef Riekenberg <wine.dev(a)web.de> wrote: > static HRESULT WINAPI DEVENUM_IMediaCatMoniker_BindToStorage(IMoniker *iface, IBindCtx *pbc, > IMoniker *pmkToLeft, REFIID riid, void **ppvObj) > { > + static IBindCtx *old_bc; > MediaCatMoniker *This = impl_from_IMoniker(iface); > > TRACE("(%p)->(%p, %p, %s, %p)\n", This, pbc, pmkToLeft, debugstr_guid(riid), ppvObj); > > *ppvObj = NULL; > > - if (pbc || pmkToLeft) > + if (pbc != old_bc) > + { > + FIXME("ignoring IBindCtx %p\n", pbc); > + old_bc = pbc; > + } This doesn't look sane. -- Dmitry.

1 0

wine/clang warnings
by Austin English May 15, 2012

May 15, 2012

Howdy, I tried Wine with LLVM/Clang from svn recently, thought others may like some of the results. I've also ran the static analyzer. For reference, this is with: wine-1.5.4-61-g8327e6f, plus the following patch: diff --git a/include/windef.h b/include/windef.h index 9cf98e7..e95388a 100644 --- a/include/windef.h +++ b/include/windef.h @@ -53,7 +53,7 @@ extern "C" { #ifndef __stdcall # ifdef __i386__ # ifdef __GNUC__ -# ifdef __APPLE__ /* Mac OS X uses a 16-byte aligned stack and not a 4-byte one */ +# if defined (__APPLE__) || defined (__clang__) /* Mac OS X uses a 16-byte aligned stack and not a 4-byte one */ # define __stdcall __attribute__((__stdcall__)) __attribute__((__force_align_arg_pointer__)) # else # define __stdcall __attribute__((__stdcall__)) see http://wiki.winehq.org/Clang for more info. Wine was compiled using: #!/bin/bash export CC="clang" export CXX="$CC" export CFLAGS="-g -O0 -std=gnu89 -Wno-conversion -Wno-invalid-source-encoding" ./configure -Wno-invalid-source-encoding, because clang does not like our encoding of strings in winex11/keyboard.c. There are 851 warnings of: clang -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Wstrict-prototypes -Wtype-limits -Wwrite-strings -fno-omit-frame-pointer -Wpointer-arith -I/usr/include/freetype2 -g -O0 -std=gnu89 -Wno-conversion -o keyboard.o keyboard.c keyboard.c:267:17: warning: illegal character encoding in string literal [-Winvalid-source-encoding] "`","1!","2\"","3<A3>","4$","5%","6^","7&","8*","9(","0)","-_","=+", The static analyzer found 2231 bugs (--disable-tests was used). http://www.sendspace.com/file/qsbv3k austin(a)aw21 ~ $ du -h scan-build-2012-05-15-2.tar.bz2 42M scan-build-2012-05-15-2.tar.bz2 austin(a)aw21 ~ $ sha1sum scan-build-2012-05-15-2.tar.bz2 442cf6faddb45515792d116717c992282496dfbe scan-build-2012-05-15-2.tar.bz2 Cheers, Austin

1 0

Re: comctl32: Fix message sequence when right-clicking a treeview
by Nikolay Sivov May 15, 2012

May 15, 2012

On 5/15/2012 21:30, Daniel Jelinski wrote: > Patch dropped out of the pending list, resending. Please add a test for this fix.

2 2

Re: [PATCH 1/3] user32: Added GetMenuBarInfo implementation (try2)
by Alexandre Julliard May 15, 2012

May 15, 2012

Piotr Caban <piotr(a)codeweavers.com> writes: > This patch serie is based on Andrew Eikum's and Rein Klazes's work. > --- > dlls/user32/menu.c | 94 > ++++++++++++++++++++++++++++++++++++++++++++++++---- > 1 files changed, 87 insertions(+), 7 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so msg.c && touch msg.ok msg.c:11511: Tests skipped: Skipping DBCS WM_CHAR test in SBCS codepage 'ANSI Latin 1' msg.c:12297: Test failed: popup menu command: 17: the msg 0x011f was expected, but got msg 0x0004 instead msg.c:12297: Test failed: popup menu command: 18: the msg 0x0212 was expected, but got msg 0x011f instead msg.c:12297: Test failed: popup menu command: 19: the msg 0x0126 was expected, but got msg 0x0212 instead msg.c:12297: Test failed: popup menu command: 21: the msg 0x0101 was expected, but got msg 0x0126 instead msg.c:12297: Test failed: popup menu command: 22: the msg sequence is not complete: expected 0000 - actual 0101 msg.c:12315: Test failed: submenu of a popup menu command: 22: the msg 0x0004 was expected, but got msg 0x0125 instead msg.c:12315: Test failed: submenu of a popup menu command: 23: the msg 0x0125 was expected, but got msg 0x0004 instead msg.c:12315: Test failed: submenu of a popup menu command: 26: the msg 0x011f was expected, but got msg 0x0004 instead msg.c:12315: Test failed: submenu of a popup menu command: 27: the msg 0x0212 was expected, but got msg 0x011f instead msg.c:12315: Test failed: submenu of a popup menu command: 28: the msg 0x0126 was expected, but got msg 0x0212 instead msg.c:12315: Test failed: submenu of a popup menu command: 30: the msg 0x0101 was expected, but got msg 0x0126 instead msg.c:12315: Test failed: submenu of a popup menu command: 31: the msg sequence is not complete: expected 0000 - actual 0101 msg.c:12363: Test failed: submenu of a popup menu command: 22: the msg 0x0004 was expected, but got msg 0x0125 instead msg.c:12363: Test failed: submenu of a popup menu command: 23: the msg 0x0125 was expected, but got msg 0x0004 instead msg.c:12363: Test failed: submenu of a popup menu command: 26: the msg 0x011f was expected, but got msg 0x0004 instead msg.c:12363: Test failed: submenu of a popup menu command: 27: the msg 0x0212 was expected, but got msg 0x011f instead msg.c:12363: Test failed: submenu of a popup menu command: 28: the msg 0x0111 was expected, but got msg 0x0212 instead msg.c:12363: Test failed: submenu of a popup menu command: 30: the msg 0x0101 was expected, but got msg 0x0111 instead msg.c:12363: Test failed: submenu of a popup menu command: 31: the msg sequence is not complete: expected 0000 - actual 0101 make[1]: *** [msg.ok] Error 19 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: ddraw: Forward AddAttachedSurface to the correct equivalent
by Stefan Dösinger May 15, 2012

May 15, 2012

Am Sonntag, 13. Mai 2012, 20:39:27 schrieb David Adam: > + hr = ddraw_surface3_AddAttachedSurface(&This- >IDirectDrawSurface3_iface, > + attachment_impl ? &attachment_impl->IDirectDrawSurface3_iface : NULL); It isn't immediately clear to me why Surface3 is correct instead of Surface7. Do you have tests or bug reports to back this up?

3 3

Re: [PATCH 1/4] dsound: Remove minlen, since we always mix full chunks anyway
by Alexander E. Patrakov May 15, 2012

May 15, 2012

Andrew Eikum wrote: > - > - TRACE("Mixed at least %d from all buffers\n", minlen); > - return minlen; Hi. You have removed the message that could say "Mixed at least 0 from all buffers" (as seen, e.g., for Armored Fist 3 and sometimes even for foobar2000). What was the reason for that "0" (or, rather, 1024, 1024, 1024, 0, 2048, 1024, ... sequence) seen in some games? Was it also fixed by your patch? (this mail is a question, not an objection) -- Alexander E. Patrakov

2 1

Re: [PATCH 1/4] dsound: Change mix_buffer to float instead of INT
by Alexander E. Patrakov May 15, 2012

May 15, 2012

Andrew Eikum wrote: > +static LONG f_to_24(float value) > +{ > if(value <= -1.f) > + return 0x80000000; > + if(value >= 1.f * 0x7FFFFF / 0x800000) > + return 0x7FFFFF00; > + return lrintf(value * 0x80000000U); > } ... > +static inline LONG f_to_32(float value) > +{ > + if(value <= -1.f) > + return 0x80000000; > + if(value >= 1.f * 0x7FFFFFFF / 0x80000000U) /* this rounds to 1.f */ > + return 0x7FFFFFFF; > + return le32(lrintf(value * 0x80000000U)); > +} [sorry for a possible duplicate, the previous mail contained a typo] Minor nitpick: I'd say these functions are identical on little-endian systems if the least significant bits are discarded. Are you sure that we indeed want two functions here, and not, say, use f_to_32() in put24()? -- Alexander E. Patrakov

1 0

Wine Mono 0.0.4 Release - I'm serious now!
by Vincent Povirk May 14, 2012

May 14, 2012

I have published version 0.0.4 of Wine Mono on Sourceforge. I fully intend to make this release a part of Wine. The source tarball is at http://sourceforge.net/projects/wine/files/Wine%20Mono/0.0.4/wine-mono-0.0.… The binary is at http://sourceforge.net/projects/wine/files/Wine%20Mono/0.0.4/wine-mono-0.0.… For developers, the source repository is at https://github.com/madewokherd/wine-mono Changes since 0.0.2: * With Wine 1.5.4 and Wine Mono 0.0.4, it's now possible to run mixed-mode assemblies. * The random hang that was introduced in Mono 2.11 is now fixed (0.0.2 contained a hacky work-around). * A replacement for XNA 4.0 based on MonoGame is now included, to be used if MS XNA 4.0 is not installed. * Updated Mono from 2.11.0 to 2.11.1, bringing in the changes listed here: http://mono.1490590.n4.nabble.com/Mono-2-11-1-is-out-td4575466.html * Changes from Hans Leidekker to make upgrading and removing the msi work better. * Added more registry keys to prevent native .NET from trying to install while Wine Mono is installed. * Various improvements to the build script. Some programs that worked with the official Mono for Windows package will fail with this one because gluezilla (Mono's web browser component) is missing. In all other respects I expect this to work as well as or better than the official Mono for Windows package, and if not I'd like to hear about it. If nothing new seems to be horribly wrong with this build other than the lack of gluezilla, I will try to make it an official part of Wine. It's not really clear where the bugs should be reported at the moment, but I think Wine bugzilla is appropriate.

1 0

XINPUT JOYSTICK PATCH
by Giovanni Ongaro May 14, 2012

May 14, 2012

I have written a modification of the xinput1_3 dll that simulates xbox joystick with a logitech rumblepad 2 joystick,also provided is a way to disable dinput joysticks through an environment variable, it seems to work well,may it be of interest to the wine project?

2 1

Re: wmvcore: Add stub for WMCreateSyncReader
by Nikolay Sivov May 14, 2012

May 14, 2012

On 5/14/2012 19:34, André Hentschel wrote: > Otherwise GTA San Andreas runs into it and crashes. This stub let's it work again. > a workaround is to disable wmvcore in winecfg... > --- > dlls/wmvcore/wmvcore.spec | 2 +- > dlls/wmvcore/wmvcore_main.c | 8 ++++++++ > 2 files changed, 9 insertions(+), 1 deletions(-) > > diff --git a/dlls/wmvcore/wmvcore.spec b/dlls/wmvcore/wmvcore.spec > index 1c6cb1f..e0fa2e9 100644 > --- a/dlls/wmvcore/wmvcore.spec > +++ b/dlls/wmvcore/wmvcore.spec > @@ -11,7 +11,7 @@ > @ stub WMCreateProfileManager > @ stub WMCreateReader > @ stub WMCreateReaderPriv > -@ stub WMCreateSyncReader > +@ stdcall WMCreateSyncReader(ptr long ptr) > @ stub WMCreateWriter > @ stub WMCreateWriterFileSink > @ stub WMCreateWriterNetworkSink > diff --git a/dlls/wmvcore/wmvcore_main.c b/dlls/wmvcore/wmvcore_main.c > index 096328b..5fce972 100644 > --- a/dlls/wmvcore/wmvcore_main.c > +++ b/dlls/wmvcore/wmvcore_main.c > @@ -22,6 +22,7 @@ > > #include "windef.h" > #include "winbase.h" > +#include "objbase.h" > #include "wine/debug.h" > > WINE_DEFAULT_DEBUG_CHANNEL(wmvcore); > @@ -43,3 +44,10 @@ BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved) > > return TRUE; > } > + > +HRESULT WINAPI WMCreateSyncReader(IUnknown *pcert, DWORD rights, > + IUnknown /* FIXME: IWMSyncReader */ **syncreader) > +{ > + FIXME("(%p, %x, %p): stub\n", pcert, rights, syncreader); > + return E_NOTIMPL; > +} You'll be probably requested to add a proper .idl for that with interface definition. Also it makes sense to init out parameter to 0, as a common practice for such creation methods/calls. >

1 0

Re: [1/2] gdiplus: Measure the passed in string without height clipping in order to compute correct Y offset. Take 3.
by Vincent Povirk May 14, 2012

May 14, 2012

Looks good to me.

1 0

Re: Using an IDE on Wine?
by Michael Ost May 14, 2012

May 14, 2012

On 5/13/12 10:00 AM, wine-devel-request(a)winehq.org wrote: > How many of you use an Integrated Development Environment (IDE) when > working on Wine? > > If you do, which one do you use and how, how useful is it and how hard > was it to set up? I use Qt Creator for Linux for our winelib application. Our app is a hybrid winelib + Qt/X11 app, so we get the extra Qt "goodies" with Qt Creator. But it does work for other project types too. Getting the integrated gdb debugger to work was a trick. The main thing is to set WINELOADERNOEXEC=1 in the environment and run /usr/bin/wine as the debuggee. We also built and copied in a debug version of /usr/bin/wine to keep Qt Creator from complaining when a debug session got underway. The last "gotcha" was that we had to hack out alpha channel support for cursors when running under GDB. (IIRC) the DIB engine uses segfaults in normal operation which confuses GDB. I can send along that patch if you are interested. Of course, if you are trying to debug a straight windows application then all of this is irrelevant! But if you are doing winelib, then these tricks can help. -- Michael Ost

1 0

Re: [1/2] gdiplus: Measure the passed in string without clipping in order to compute correct Y offset. Take 2.
by Vincent Povirk May 14, 2012

May 14, 2012

If the string wraps, and you don't give the width to GdipMeasureString, won't it return a too small height? On Mon, May 14, 2012 at 9:11 AM, Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > GdipMeasureString() clips the string extents to passed rectangle width and > height, but that leads to wrong offsety calculation if the string doesn't > fit into that rectangle. > --- > dlls/gdiplus/graphics.c | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/dlls/gdiplus/graphics.c b/dlls/gdiplus/graphics.c > index 38335a8..1c9780d 100644 > --- a/dlls/gdiplus/graphics.c > +++ b/dlls/gdiplus/graphics.c > @@ -5162,14 +5162,18 @@ GpStatus WINGDIPAPI GdipDrawString(GpGraphics *graphics, GDIPCONST WCHAR *string > /* Should be no need to explicitly test for StringAlignmentNear as > * that is default behavior if no alignment is passed. */ > if(format->vertalign != StringAlignmentNear){ > + static const RectF empty_rect = { 0.0, 0.0, 0.0, 0.0 }; > RectF bounds; > - GdipMeasureString(graphics, string, length, font, rect, format, &bounds, 0, 0); > + GdipMeasureString(graphics, string, length, font, &empty_rect, format, &bounds, 0, 0); > + > + TRACE("bounds %s\n", debugstr_rectf(&bounds)); > > if(format->vertalign == StringAlignmentCenter) > offsety = (rect->Height - bounds.Height) / 2; > else if(format->vertalign == StringAlignmentFar) > offsety = (rect->Height - bounds.Height); > } > + TRACE("vertical align %d, offsety %f\n", format->vertalign, offsety); > } > > save_state = SaveDC(hdc); > -- > 1.7.10.1 > > >

2 3

Re: [PATCH 1/5] d3dcompiler: Make SlWriteBytecode return the shader size.
by Stefan Dösinger May 14, 2012

May 14, 2012

Am Montag, 14. Mai 2012, 17:24:01 schrieb Matteo Bruni: > - CopyMemory(pos, messages, strlen(messages) + 1); > + memcpy(pos, messages, strlen(messages) + 1); > ... > - if (shader == NULL) > + if (!shader) This looks unrelated. The changes are OK, but should be in another patch.

1 0

Re: [1/3] user32/tests: Add GetUserObjectInformation tests
by Alexandre Julliard May 14, 2012

May 14, 2012

Owen Rudge <orudge(a)codeweavers.com> writes: > There appears to be a bug in the GetUserObjectInformationA function on > Windows that results in an incorrect buffer length being returned when > the buffer size provided by the caller is insufficient. The 'A' > function returns the Unicode length instead of the ANSI length. These > patches modify Wine's behaviour to provide that incorrect > behaviour. They also fix an issue whereby the wrong error code is set > when the buffer is too short. Using the number of Unicode chars multiplied by 2 is a reasonable upper bound on the A string size, and it's used in a number of places. This can't really be considered a Windows bug. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: [1/2] gdiplus: Measure the passed in string without clipping in order to compute correct Y offset.
by Vincent Povirk May 14, 2012

May 14, 2012

> - GdipMeasureString(graphics, string, length, font, rect, format, &bounds, 0, 0); > + GdipMeasureString(graphics, string, length, font, &bounds, format, &bounds, 0, 0); You probably shouldn't use the same GpRect* for both parameters there.

2 3

Re: msxml3: avoid a dangling else (LLVM/Clang)
by Michael Stefaniuc May 14, 2012

May 14, 2012

Hello Austin, On 05/14/2012 08:01 AM, Austin English wrote: > diff --git a/dlls/msxml3/domdoc.c b/dlls/msxml3/domdoc.c > index 6805c75..14fd01b 100644 > --- a/dlls/msxml3/domdoc.c > +++ b/dlls/msxml3/domdoc.c > @@ -2277,8 +2277,10 @@ static HRESULT WINAPI domdoc_loadXML( > > /* skip leading spaces if needed */ > if (This->properties->version == MSXML_DEFAULT || This->properties->version == MSXML26) > + { > while (*ptr) > if (isspaceW(*ptr)) ptr++; else break; I do not mind terse code but that kinda overdoes it. I would put the "else" on a separate line. > + } > > xmldoc = doparse(This, (char*)ptr, strlenW(ptr)*sizeof(WCHAR), XML_CHAR_ENCODING_UTF16LE); > if ( !xmldoc ) bye michael

2 2

Re: wininet: Fixed typo in tests and accompanying implementation
by Marvin May 14, 2012

May 14, 2012

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=18349 Your paranoid android. === W7PROX64 (64 bit http) === http.c:2853: Test failed: HttpSendRequest failed: 12002

1 0

Re: wininet/tests: fix a compiler warning on LLVM/Clang
by Jacek Caban May 14, 2012

May 14, 2012

Hi Austin, On 05/14/12 08:19, Austin English wrote: > clang -c -I. -I. -I../../../include -I../../../include > -DWINE_STRICT_PROTOTYPES -DWINE_NO_NAMELESS_EXTENSION -D_REENTRANT > -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement > -Wempty-body -Wignored-qualifiers -Wstrict-prototypes -Wtype-limits > -Wwrite-strings -fno-omit-frame-pointer -Wpointer-arith > -I/usr/include/freetype2 -g -O0 -std=gnu89 -o http.o http.c > http.c:212:52: warning: use of logical '||' with constant operand > [-Wconstant-logical-operand] > res = HttpQueryInfo(req, > HTTP_QUERY_STATUS_CODE||HTTP_QUERY_FLAG_NUMBER, &code, &size, &index); > ^ ~~~~~~~~~~~~~~~~~~~~~~ > http.c:212:52: note: use '|' for a bitwise operation > res = HttpQueryInfo(req, > HTTP_QUERY_STATUS_CODE||HTTP_QUERY_FLAG_NUMBER, &code, &size, &index); > ^~~~~~~~~~~~~~~~~~~~~~~~ > | > http.c:218:52: warning: use of logical '||' with constant operand > [-Wconstant-logical-operand] > res = HttpQueryInfo(req, > HTTP_QUERY_STATUS_CODE||HTTP_QUERY_FLAG_REQUEST_HEADERS, &code, &size, > NULL); > ^ > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > http.c:218:52: note: use '|' for a bitwise operation > res = HttpQueryInfo(req, > HTTP_QUERY_STATUS_CODE||HTTP_QUERY_FLAG_REQUEST_HEADERS, &code, &size, > NULL); > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Thanks for the patch. The problem found by those warnings was more serious as we were tested a wrong thing, causing the implementation to be wrong. That said, we need to fix tests and implementation as well. I've sent a patch. Thanks, Jacek

1 0

Re: wininet/tests: fix a compiler warning on LLVM/Clang
by Marvin May 14, 2012

May 14, 2012

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=18347 Your paranoid android. === WXPPROSP3 (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === W2K3R2SESP2 (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === WVISTAADM (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === W2K8SE (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === W7PRO (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === W7PROX64 (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === TEST64_W7SP1 (32 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === W7PROX64 (64 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) === TEST64_W7SP1 (64 bit http) === http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154) http.c:1920: Test failed: HttpQueryInfo failed: 0(12154) http.c:1970: Test failed: HttpQueryInfo failed: 0(12154) http.c:2021: Test failed: HttpQueryInfo failed: 0(12154) http.c:2076: Test failed: HttpQueryInfo failed: 0(12154) http.c:2086: Test failed: HttpQueryInfo failed: 0(12154) http.c:2096: Test failed: HttpQueryInfo failed: 0(12154) http.c:2106: Test failed: HttpQueryInfo failed: 0(12154) http.c:2350: Test failed: HttpQueryInfo failed: 0(12154) http.c:2380: Test failed: HttpQueryInfo failed: 0(12154) http.c:2406: Test failed: HttpQueryInfo failed: 0(12154) http.c:2456: Test failed: HttpQueryInfo failed: 0(12154) http.c:2541: Test failed: HttpQueryInfo failed: 0(12154) http.c:476: Test failed: HttpQueryInfo failed: 0(12154)

1 0

Re: [2/2] msxml3: Support iso-8859-x encodings in writer
by Marvin May 14, 2012

May 14, 2012

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=18346 Your paranoid android. === W2KPROSP4 (32 bit saxreader) === saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-3: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?> saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-4: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?> saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-5: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?> saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-7: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?> saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-9: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?> saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-13: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?> === WXPPROSP3 (32 bit saxreader) === saxreader.c:3759: Test failed: got 0x80004005, expected 0x00000000 saxreader.c:3780: Test failed: iso-8859-3: got <?xml version="1.0" encoding="iso-8859-2" standalone="no"?>

1 0

Re: jscript/tests: Fix the spelling of the testEmbeddedFunctions() function name.
by Marvin May 13, 2012

May 13, 2012

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=18345 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: jscript/tests: Fix the spelling of the testEmbeddedFunctions() function name.
by Marvin May 13, 2012

May 13, 2012

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

Using an IDE on Wine?
by Max TenEyck Woodbury May 13, 2012

May 13, 2012

How many of you use an Integrated Development Environment (IDE) when working on Wine? If you do, which one do you use and how, how useful is it and how hard was it to set up? Max

4 3

re: Using an IDE on Wine?
by Dan Kegel May 13, 2012

May 13, 2012

I suspect most people don't use IDEs with wine. Someone recently posted how to use eclipse during debugging, though: http://www.winehq.org/pipermail/wine-devel/2012-April/095162.html

1 0