wine-devel July 2012

wine-devel@winehq.org

69 participants
314 discussions

Have there been any problems with Wine on GCC 4.7?
by Scott Ritchie 23 Aug '12

23 Aug '12

Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well. But now we have 4.7 -- have there been any bugs attributed to its usage? Thanks, Scott Ritchie

4 15

Re: user32: search more aggressively for a window under a tooltip
by Dmitry Timoshkov 14 Aug '12

14 Aug '12

Daniel Jelinski <djelinski1(a)gmail.com> wrote: > Fixes bug 9512 and bug 8914, tested with Delphi and DVD Profiler. > Still not perfect - according to MSDN the function should never return > a window belonging to another thread. This kind of change requires a test case, and I suspect it's plain wrong. -- Dmitry.

3 9

__wine_uuidof causing a wall of "warning: returning reference to temporary" on g++
by Ilya Konstantinov 08 Aug '12

08 Aug '12

Hi, I've just started porting my C++ application to Linux with Winelib. Upon first attempts to compile, I've received a wall of "warning: returning reference to temporary" on Wine's headers from g++. All of those seem to stem from guidgen.h definition of __wine_uuidof / __CRT_UUID_DECL for C++. All in all, g++ seems to be right -- we are indeed returning a reference to a IID struct that's allocated on the stack. If I remove the '&' in this definition (in guidgen.h): template<typename T> const GUID &__wine_uuidof(); the warnings stop, but then I wonder, did the original author have some good reasoning for returning a reference in the first place? Thanks.

2 4

Wine automated testing update
by Jeremy White 06 Aug '12

06 Aug '12

Hi Folks, At the last Wine conference, I volunteered to find a home for the WineTestBot that Ge's brother has been hosting, and to take over the Buildbot that Dan and Austin have been so diligently maintaining. This is an update on that project, mostly to help keep my procrastinating self moving it along. First, we have a lovely set of hardware; 4 servers, in a dedicated rack, with a dedicated static ip to the outside world. One server is the gateway, 2 are dedicated Linux test systems (with nice fast processor + gpus), and one is a beefy system capable of running many VMs. The plan was to move the existing VMWare based WineTestBot to this hardware and simply get the existing system up and running on the new hardware. Here we hit our first snag; the VMWare folks are not willing to provide a permanent license for VMWare to us. So, we've shifted gears, and are exploring whether something like qemu + kvm would be a sufficient alternate. I've done a little of this work, and Maarten is hopefully going to help me try converting the existing VMs to see if we can save any hassle by doing a conversion. In parallel, I learned a great deal about buildbot and the buildbot system that Dan has built. There are two especially valuable and useful functions provided by this buildbot: the first is essentially a patch watcher; a process that catches simple mistakes (e.g. build errors on different architectures, and so on). The second is more powerful and is encapsulated by the 'dotests.sh' shell script. The dotests.sh script does a good job of basically running make test and noticing any test failures outside of 'the usual ones'. There is an infrastructure for Buildbot is a good tool, and I invested a lot of energy into it (as have Dan and Austin). However, Alexandre has persuaded me that we should first explore integrating the dotest.sh functionality into the existing WineTestBot, as that would allow us to have a very simple clean web page, and would also allow us to integrate most cleanly with Alexandre's back end tools. Of course, WineTestBot is Perl code, and my Perl fu is low. So I have recently asked Francois to help with that effort as well. So the basic plan is as follows: 1. Test qemu/kvm with a few Windows versions to see if it'll work. 2. If so, modify WineTestBot to use qemu instead of vmware. (This is 'easy' because the WineTestBot code nicely isolates the VM functions, but 'hard', because VMWare provides some APIs that may have to be replicated). 3. Migrate WineTestBot to the new hardware stack 4. Write new code to run 'dotests.sh' as part of WineTestBot Cheers, Jeremy

9 11

GSoC mentor summit 2012
by Owen Rudge 06 Aug '12

06 Aug '12

It looks like the GSoC mentor summit for 2012 has been announced. Are any of the mentors this year interested in attending? It's happening on the 20th/21st October in Mountain View. Details are on the GSoC mentor wiki: http://gsoc-wiki.osuosl.org/index.php/2012 Cheers, -- Owen Rudge http://www.owenrudge.net/

6 10

"Complimentary" msvcrt?
by Ilya Konstantinov 31 Jul '12

31 Jul '12

Hey, I apologize for the flood of "newbie" questions coming from me lately :-) At the very least, I'll be giving Winelib a decent challenge, and perhaps we could improve it a bit... Now, I've seen that Wine re-implements MSVCRT. However, this is a drop-in MSVCRT.DLL replacement, and it's incompatible with the rest of the GNU toolchain; for example, the GNU libstdc++ barfs on trying to include its own <wchar.h> and ending up including the msvcrt/wchar.h instead. I'm looking for something more humble -- a library for easy porting, implementing those functions not implemented by glibc itself -- e.g. _wfopen, _wgetenv. In fact, many MSVCRT functions can be made available by simply #define-ing them to their glibc counterparts. (Of course, this should be done carefully.) The main goal of this library should be source-level compatibility. Does such a thing exist? P.S. I know "real men" port their code to "real glibc", but I believe in taking small steps for bringing Linux into our codebase, thus decreasing friction with the rest of the developers.

2 7

Re: [2/2] msi: Try the registered install location first when resolving the target directory.
by Alexandre Julliard 31 Jul '12

31 Jul '12

Hans Leidekker <hans(a)codeweavers.com> writes: > --- > dlls/msi/action.c | 18 +++++++++++++++--- > dlls/msi/msipriv.h | 1 + > 2 files changed, 16 insertions(+), 3 deletions(-) It doesn't work here: ../../../../wine/tools/runtest -q -P wine -M msi.dll -T ../../.. -p msi_test.exe.so ../../../../wine/dlls/msi/tests/package.c && touch package.ok wine: Unhandled page fault on read access to 0x20006308e at address 0x2b39152590cf (thread 002c), starting debugger... Unhandled exception: page fault on read access to 0x20006308e in 64-bit code (0x00002b39152590cf). Register dump: rip:00002b39152590cf rsp:000000000022f700 rbp:0000000000000001 eflags:00010246 ( R- -- I Z- -P- ) rax:0000000000063090 rbx:0000000000000002 rcx:00000000000666c2 rdx:0000000000000000 rsi:0000000000000000 rdi:0000000000000001 r8:0000000000000010 r9:000000000022f790 r10:000000000022f740 r11:000000020006308e r12:0000000000062f10 r13:0000000000000000 r14:000000000005f1f8 r15:00002b39136f0d90 Stack dump: 0x000000000022f700: 0000000000000000 0000000000000000 0x000000000022f710: 0000000000000000 0000000000000000 0x000000000022f720: 0000000000000000 0000000000000008 0x000000000022f730: 000000000022f790 000000000022f740 0x000000000022f740: 00002b39136f0d90 00000000000666c0 0x000000000022f750: 00000000000658e0 0000000000063042 0x000000000022f760: 0000000000000054 000000000005f228 0x000000000022f770: 0000000000000000 0000000000065810 0x000000000022f780: 000000000005f190 00002b391525ae9c 0x000000000022f790: 0000000000000000 0000000000000000 0x000000000022f7a0: 00002b39136f0d90 00002b391528a1fc 0x000000000022f7b0: 0000000000064f00 0000000000000030 Backtrace: =>0 0x00002b39152590cf msi_build_directory_name+0x25f(count=0x2) [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/action.c:2157] in msi (0x0000000000000001) 1 0x00002b391525ae9c ACTION_CostFinalize+0x35b(package=0x5f190) [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/action.c:2179] in msi (0x000000000005f190) 2 0x00002b391524e45b ACTION_HandleStandardAction+0xba(package=0x5f190, action="CostFinalize", rc=0x22f85c) [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/action.c:7397] in msi (0x000000000022f85c) 3 0x00002b391525d877 ACTION_PerformUIAction+0x46(package=0x5f190, action="CostFinalize", script=0xffffffff) [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/action.c:7448] in msi (0x0000000000059f20) 4 0x00002b391528b1d3 MsiDoActionW+0xc2(hInstall=0x2, szAction="CostFinalize") [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/install.c:108] in msi (0x0000000000000057) 5 0x00002b391528b436 MsiDoActionA+0x105(hInstall=0x2, szAction="CostFinalize") [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/install.c:56] in msi (0x00002b3914b9af00) 6 0x00002b3914b5fabe func_package+0x45cd() [/home/julliard/wine/build/obj-elf64/dlls/msi/tests/../../../../wine/dlls/msi/tests/package.c:3017] in msi_test (0x000000000022fadc) 7 0x00002b3914a922aa main+0x2c9(argc=<internal error>, argv=<internal error>) [/home/julliard/wine/build/obj-elf64/dlls/msi/tests/../../../../wine/include/wine/test.h:557] in msi_test (0x00002b3914dc2fe0) 8 0x00002b3914b7b1b2 __wine_spec_exe_entry+0xa1(peb=<internal error>) [/home/julliard/wine/build/obj-elf64/dlls/winecrt0/../../../wine/dlls/winecrt0/exe_entry.c:36] in msi_test (0x00002b39131238f0) 9 0x000000007b873391 start_process+0xb0(peb=0x7fffffbef000) [/home/julliard/wine/build/obj-elf64/dlls/kernel32/../../../wine/dlls/kernel32/process.c:1052] in kernel32 (0x00002b3914b7b110) 10 0x00002b39139889de call_thread_func+0x6d(entry=0x7b8732e0, arg=0x7fffffbef000, frame=<internal error>) [/home/julliard/wine/build/obj-elf64/dlls/ntdll/../../../wine/dlls/ntdll/signal_x86_64.c:3230] in ntdll (0x00007fff5dbb09f0) 11 0x00002b39139820ca call_thread_entry_point+0x29() in ntdll (0x00007fff5dbb09f0) 12 0x00002b39139549d6 start_process+0x15(kernel_start=<internal error>) [/home/julliard/wine/build/obj-elf64/dlls/ntdll/../../../wine/dlls/ntdll/loader.c:2653] in ntdll (0x00007fff5dbb09f0) 13 0x00002b3912dfd283 wine_call_on_stack+0x12() in libwine.so.1 (0x00007fff5dbb09f0) 14 0x00002b3912dfd2d9 wine_switch_to_stack+0x8(func=<internal error>, arg=<internal error>, stack=<internal error>) [/home/julliard/wine/build/obj-elf64/libs/wine/../../../wine/libs/wine/port.c:59] in libwine.so.1 (0x00007fffffbef000) 15 0x00002b391395a480 LdrInitializeThunk+0x45f(kernel_start=0x7b8732e0, unknown2=<internal error>, unknown3=<internal error>, unknown4=<internal error>) [/home/julliard/wine/build/obj-elf64/dlls/ntdll/../../../wine/dlls/ntdll/loader.c:2709] in ntdll (0x00007fffffbef000) 16 0x000000007b8797ed __wine_kernel_init+0x91c() [/home/julliard/wine/build/obj-elf64/dlls/kernel32/../../../wine/dlls/kernel32/process.c:1255] in kernel32 (0x00002b3913bea620) 17 0x00002b391395acf4 __wine_process_init+0x143() [/home/julliard/wine/build/obj-elf64/dlls/ntdll/../../../wine/dlls/ntdll/loader.c:2918] in ntdll (0x00007fff5dbb1ca0) 18 0x00002b3912dfb488 wine_init+0x297(argc=0x3, argv=0x7fff5dbb2198, error="", error_size=0x400) [/home/julliard/wine/build/obj-elf64/libs/wine/../../../wine/libs/wine/loader.c:831] in libwine.so.1 (0x00007fff5dbb1ca0) 19 0x000000007bf00da2 main+0x71(argc=0x3, argv=0x7fff5dbb2198) [/home/julliard/wine/build/obj-elf64/loader/../../wine/loader/main.c:230] in <wine-loader> (0x00007fff5dbb2198) 20 0x00002b391338dead __libc_start_main+0xfc(main=<is not available>, argc=<is not available>, ubp_av=<is not available>, init=<is not available>, fini=<is not available>, rtld_fini=<is not available>, stack_end=0x7fff5dbb2188) [/home/aurel32/eglibc/eglibc-2.13/csu/libc-start.c:228] in libc.so.6 (0x0000000000000000) 21 0x000000007bf00e9d _start+0x28() in <wine-loader> (0x0000000000000000) 0x00002b39152590cf msi_build_directory_name+0x25f [/home/julliard/wine/build/obj-elf64/dlls/msi/../../../wine/dlls/msi/action.c:2157] in msi: cmpw $5c,(%r11) 2157 if ( i + 1 != count && dir[strlenW( dir ) - 1] != '\\') strcatW( dir, szBackSlash ); -- Alexandre Julliard julliard(a)winehq.org

1 0

Error 123
by Zachary Shields 31 Jul '12

31 Jul '12

Hi, I just installed Wine on my comp and everything went well. However, when I installed my program and try to open it it gives me the error: Unable to open com port (win error code: 123) Anyone have any ideas on how to fix this? Thanks, Zachary -- Zachary Nischan Shields 317.627.3628 NischanPictures.com

2 1

Re: vbscript/tests: Use proper helpers for iface calls
by Marvin 31 Jul '12

31 Jul '12

1 0

Re: fusion: Use inline wrappers for calling COM methods.
by Marvin 31 Jul '12

31 Jul '12

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

Jump to page:

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 July 2012