January 2015 - Wine-Devel - list.winehq.org

Re: dplayx: Cache GUID values so they persist after enumeration
by Marvin Jan. 15, 2015

Jan. 15, 2015

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=11147 Your paranoid android. === w8 (32 bit dplayx) === The test timed out

1 0

Mac Driver's functionality on Snow Leopard/Lion
by António Sarmento Jan. 14, 2015

Jan. 14, 2015

Hello everyone, I had a question about the functionality of the Mac Driver when I found out that winemac.drv.so wasn’t working on my machine with Snow Leopard with a Wine wrapper; this was partially discussed in another e-mail sent directly to Ken Thomases (I apologize for this, I should’ve found the use of this mailing list sooner), where I mentioned that the addition of kCGDisplayShowDuplicateLowResolutionModes was keeping Wine from creating windows on OS X 10.6 (building works, Wine just stops at loading winemac.drv.so), as specified in this log: err:module:load_builtin_dll failed to load .so lib for builtin L"winemac.drv": dlopen(/path/to/app/Contents/Frameworks/wswine.bundle/bin/../lib/wine/winemac.drv.so, 258): Symbol not found: _kCGDisplayShowDuplicateLowResolutionModes Referenced from: /path/to/app/Contents/Frameworks/wswine Application tried to create a window, but no driver could be loaded. Unknown error (127). wine: Unhandled exception 0x0eedfade in thread 9 at address 0x0000:0x7b82cda2 (thread 0009), starting debugger... Application tried to create a window, but no driver could be loaded. Unknown error (127). err:seh:setup_exception_record stack overflow 2016 bytes in thread 0009 eip 7bc3772c esp 00230b50 stack 0x230000-0x231000-0x330000 This, however, was a fault of my own since, as suggested by Ken, I should've included "-mmacosx-version-min=10.6" to the compiler flags if I wanted Snow Leopard to be included in the range of supported OS; The symbols that were causing trouble for me «might not be available at run time» now «resolve to a NULL address», so the driver is able to run (my app using winemac now crashes for another reason of which I shall make a proper research later). I doubt this particular log actually helps since it just further shows the problem trying to run winemac when it was not compiled for that OS. I shall ask more questions about the Mac Driver in the future, if there’s no problem with you. Thank you for your time! António

1 0

Re: dplayx/tests: Add DirectPlayEnumerate[A|W] tests
by Alexandre Julliard Jan. 14, 2015

Jan. 14, 2015

Bruno Jesus <00cpxxx(a)gmail.com> writes: > Required for bug https://bugs.winehq.org/show_bug.cgi?id=37185 > > Manually tested in NT4 and 98. > > Windows 8 fails and I believe it's in a dialog box asking to install > direct play, the same issue already found by Alistair Leslie-Hughes > and that he is trying to fix. As soon as he fixes it in dpnet we will > be able to copy over dplayx too. It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M dplayx.dll -p dplayx_test.exe.so dplayx && touch dplayx.ok dplayx.c:826: Test succeeded inside todo block: Expected equal GUID values dplayx.c:858: Test succeeded inside todo block: Expected equal GUID values dplayx.c:6668: Tests skipped: Run in interactive mode to run dplayx tests. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: cmd: implemented && and || functionality
by Alexandre Julliard Jan. 14, 2015

Jan. 14, 2015

Михаил Быстрянцев <ho-rr-or(a)mail.ru> writes: > Implemented expected behavior of && and || delimeters, https://bugs.winehq.org/show_bug.cgi?id=32679 It breaks the tests: ../../../tools/runtest -q -P wine -T ../../.. -M cmd.exe -p cmd.exe_test.exe.so batch && touch batch.ok batch.c:312: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 398 (got 'foo3 not created', wanted 'foo3 not created') batch.c:312: Test failed: unexpected char 0x2d position 0 in line 400 (got '--- on failure conditional or', wanted 'foo4') batch.c:304: Test failed: excess characters on line 134 (got '1 ', wanted '1') batch.c:304: Test failed: excess characters on line 137 (got '1 ', wanted '1') batch.c:304: Test failed: excess characters on line 139 (got '1 ', wanted '1') batch.c:304: Test failed: excess characters on line 141 (got '1 ', wanted '1') batch.c:304: Test failed: excess characters on line 142 (got '2 ', wanted '2') batch.c:304: Test failed: excess characters on line 144 (got '1 ', wanted '1') batch.c:304: Test failed: excess characters on line 145 (got '2 ', wanted '2') batch.c:304: Test failed: excess characters on line 148 (got '1 ', wanted '1') make[1]: *** [batch.ok] Error 10 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [resend 1/8] reg: Add system error printing function
by Jonathan Vollebregt Jan. 14, 2015

Jan. 14, 2015

This patchset has fallen off the list twice now, though Stefan looked over and OKd it both times. I'd appreciate it if you guys could take a look so I don't have to resend them again next month - thanks!

1 0

Re: [2/4] wbemdisp: Implement ISWbemObjectSet::get__NewEnum.
by Nikolay Sivov Jan. 14, 2015

Jan. 14, 2015

On 01/14/2015 05:36 PM, Hans Leidekker wrote: > --- > dlls/wbemdisp/locator.c | 156 +++++++++++++++++++++++++++++++++++++++-- > dlls/wbemdisp/tests/wbemdisp.c | 69 ++++++++++++++++++ > 2 files changed, 221 insertions(+), 4 deletions(-) > > +static HRESULT EnumVARIANT_create( ISWbemObjectSet *objectset, IEnumVARIANT **obj ) > +{ > + struct enumvar *enumvar; > + > + if (!(enumvar = heap_alloc( sizeof(*enumvar) ))) return E_OUTOFMEMORY; > + enumvar->IEnumVARIANT_iface.lpVtbl = &enumvar_vtbl; > + enumvar->refs = 1; > + enumvar->objectset = objectset; > + ISWbemObjectSet_AddRef( enumvar->objectset ); That means that all IEnumVARIANT instances share same ISWbemObjectSet, so they all depend on its current state and Next/Skip on one IEnumVARIANT affects every instance. I don't think that's how IEnumVARIANT is supposed to behave.

1 0

feedback on my valgrind related patches
by Marc Bessières Jan. 14, 2015

Jan. 14, 2015

Hello, I know you are very busy, so sorry to disturb you. One month ago I submitted 2 valgrind related patches: http://source.winehq.org/patches/data/108226 and http://source.winehq.org/patches/data/108223 I also attach them to this mail. They are still in NEW, and I think after one month they go out of the queue. According to the legend it means they've not been looked at yet. Do you know what I can do to have some feedback for them? I tried to create commit messages as complete as possible to explain each change. I didn't add any regression test, because the valgrind errors were triggered by the existing tests. I presume that was not good enough though, but I'm willing to improve if I'm given some guidance. Cheers, Marc

1 0

Text run in DirectWrite
by Julian Rüger Jan. 14, 2015

Jan. 14, 2015

Hi List, I'm having some trouble translating "text run" (in the current release notes "Better text run support in DirectWrite.") I would appreciate an explanation and/or suggestions for a German translation. Is it some kind of moving text? An iteration of some sorts over a given text or string(s)? Thanks and a happy new year to everyone! Best, Julian

2 2

Re: dplayx/tests: Add DirectPlayEnumerate[A|W] tests
by Marvin Jan. 14, 2015

Jan. 14, 2015

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=11134 Your paranoid android. === w8 (32 bit dplayx) === Failure running script in VM: timed out waiting for the child process

1 0

Re: [PATCH 2/5] winecfg: Bring back 32-bit Windows versions for 64-bit WINEPREFIXES
by Nikolay Sivov Jan. 13, 2015

Jan. 13, 2015

On 10.01.2015 21:27, Ken Sharp wrote: > winecfg: Bring back 32-bit Windows versions for 64-bit WINEPREFIXES > > Having a 64-bit WINEPREFIX shouldn't exclude you from selecting 32-bit > versions of Windows. Yes, it should. There's no such thing as 64 bit win2k or winme.

6 7