August 2005 - Wine-Devel - list.winehq.org

Re: Move Win16 relay messages to the relay16 channel

by Richard Cohen

Uwe Bonnes wrote: > Go ahead with implementing ;-) > Here is a implementation that can exclude relay calls from builtin dlls. I used '<builtin>' as the magic word because '%' is possible in file names. Calls to window procedures and DLL attach/detach are still shown, but that is the same as the original nrelay patch. > And let's add %deferred% What do mean by 'deferred'? Richard.

Aug. 3, 2005

Re: Benchmark's on the Wiki

by Tom Wickline

The DronezMark scores from a couple days back are incorrect! I had VSync set in XP and that was the reason for Wine having such a huge % increase over XP. I re-ran the test on XP and Wine with sound set to Performance and VSync turned off. XP 1024x768x32 Wine 1024x768x24 Tom

Aug. 3, 2005

fr-025

by Andreas Schneider

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, fr-25 doesn't display only a white bar in the middle. You can see the "demo" on the top, where normally a black bar is. And in the middle you se some colored vertical stripes. fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x403b50a0)->(161,1) not handled yet fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 fixme:d3d:IWineD3DStateBlockImpl_Apply Unrecognized state block type 0 This is the output which loops. -- andreas - -- http://www.linux-gamers.net - your online gaming resource -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFC8NmVf94+j/M+P8YRAr3VAJ9QNCaK/vjcE53NQXi3+BqeFoIIQgCff//3 6ytQscKf03IRxeSIRSoDDiM= =Ov44 -----END PGP SIGNATURE-----

Aug. 3, 2005

Re: WRT: Links and Timeout

by Felix Nawothnig

Francois Gouget wrote: >> On the WRT-Page "http://www.astro.gla.ac.uk/users/paulm/WRT/wrt.php", >> the link for "current status of Wine's conformance tests" is dead >> ("http://fgouget.free.fr/wine/tests-en.shtml"). > The list of tests was really a pain to manage by hand and as it has > grown a lot since then it would be much worse now. So I discontinued > that page a long time ago (more than a year). > > However I believe that some people have put up automated replacements > based on the automated test framework. So pointing to this set of pages > would be nice (sorry I don't have the URL handy). You mean http://test.winehq.com/data/ ? Felix

Aug. 3, 2005

Re: pf_vsnprintf implementatnion of 'I', 'I32' and 'I64' prefixes for type specifiers

by Wesley Parish

Just ask. The ReactOS team have been working closely with the Wine project; I don't see there's any problem. Wesley Parish On Wed, 03 Aug 2005 02:12, Jonathan Wilson wrote: > > Feel free to go ahead and write one if you like :) > > One assumes ReactOS needs such a function, how do they do it? > Would getting the ReactOS guys to re-licence as LGPL (if such a thing is > even possible) their printf base code work? (is what they have even any > use?) > > Just a thought :) -- Clinersterton beademung, with all of love - RIP James Blish ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

Aug. 3, 2005

Re: secur32: add first SSPI test to actually see what work needs to be done

by Kai Blin

* Kai Blin <blin(a)gmx.net> [03/08/05, 02:03:27]: > + sec_status = QuerySecurityPackageInfo( sec_pkg_name, &pkg_info); > + > + ok((long)sec_status >= 0L, "Return value of QuerySecurityPackageInfo should be >= 0, but is %ld\n", (long)sec_status); > + Never mind that. After running the tests on Win32, I realized I needed to check for SEC_E_OK, not 0. I'll resubmit the patch. Kai -- Kai Blin, (blin at gmx dot net) "It might help if we ran the MBA's out of Washington." -- Admiral Grace Hopper

Aug. 3, 2005

Re: Remove Win16 CurrentDirectory hack

by Richard Cohen

Alexandre Julliard wrote: > No it's not correct, the current directory needs to be per-task for > Win16 apps. > OK, I'll check why it's not being set correctly, perhaps in WinExec. Richard.

Aug. 3, 2005

Re: WRT: Links and Timeout

by Francois Gouget

On Wed, 3 Aug 2005, Detlef Riekenberg wrote: > Hi Francois and Paul. > > On the WRT-Page "http://www.astro.gla.ac.uk/users/paulm/WRT/wrt.php", > the link for "current status of Wine's conformance tests" is dead > ("http://fgouget.free.fr/wine/tests-en.shtml"). The list of tests was really a pain to manage by hand and as it has grown a lot since then it would be much worse now. So I discontinued that page a long time ago (more than a year). However I believe that some people have put up automated replacements based on the automated test framework. So pointing to this set of pages would be nice (sorry I don't have the URL handy). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels.

Aug. 3, 2005

Re: Move Win16 relay messages to the relay16 channel

by Uwe Bonnes

>>>>> "Alexandre" == Alexandre Julliard <julliard(a)winehq.org> writes: Alexandre> Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: >> For example the main program from the Xilinx ISE suite ise.exe starts >> _pn.exe. If I understand right, "RelayFromInclude"="ise.exe" will >> track relay calls of ise.exe,but not from _pn.exe. Alexandre> Sure, but "RelayFromInclude"="ise.exe;_pn.exe" will track Alexandre> both. Sure, but this requires the user to first track what's going on, then change user.reg and restart. If the error happens in a dll, this dll has also to be included in RelayFromInclude inuser.reg. Xilinx ISE is polluted with Dlls: ise71> ls bin/nt/*dll|wc 314 314 8123 With 314 possible dlls, an catch-all like %nrelay% would really come handy. >> However I can test, as "RelayFromInclude"="ise.exe" causes _pn.exe to >> crash... Alexandre> How does it crash? As ise.exe does an exit soon after _pn.exe is started, this combination is always hard to debug. Starting with winedbg. I get something like this: 000b:Ret kernel32.InterlockedExchange() retval=00000000 ret=0040d9ef 000b:Call kernel32.CreateProcessA(00000000,7b122380 "\"C:/ise71/bin/nt/_pn.exe\"",00000000,00000000,00000000,00000000,00000000,00000000,7ba9fd84,7ba9fdc8) ret=00401c82 fixme:process:CreateProcessW app (null) cmdline L"\"C:/ise71/bin/nt/_pn.exe\"" trace:relay:init_debug_lists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel;_LeaveSysLevel;_CheckNotSysLevel;gdi32.*;winex11.drv.*;ntdll.*" trace:relay:init_debug_lists RelayFromInclude = L"ise.exe" 000d:Call kernel32.__wine_kernel_init() ret=7bec5040 000b:Ret kernel32.CreateProcessA() retval=00000001 ret=00401c82 000b:Call kernel32.InterlockedExchange(0046b70c,00000001) ret=0040d9ef ... 000b:Ret PE DLL (proc=0x7beb2830,module=0x7bea0000 L"ntdll.dll",reason=PROCESS_DETACH,res=0x1) retval=1 Invalid address (0x0043b52d) for breakpoint 1, disabling it Process of pid=0x0000000a has terminated Wine-dbg>000d:Call PE DLL (proc=0x7beb2830,module=0x7bea0000 L"ntdll.dll",reason=PROCESS_ATTACH,res=0x1) 000d:Ret PE DLL (proc=0x7beb2830,module=0x7bea0000 L"ntdll.dll",reason=PROCESS_ATTACH,res=0x1) retval=1 000d:Call PE DLL (proc=0x7bb32ac6,module=0x7bb30000 L"kernel32.dll",reason=PROCESS_ATTACH,res=0x1) ... 000d:Ret PE DLL (proc=0x7af7f729,module=0x7af70000 L"shlwapi.dll",reason=PROCESS_ATTACH,res=0x1) retval=1 000d:Call PE DLL (proc=0x7afbf41a,module=0x7afb0000 L"MFC71.DLL",reason=PROCESS_ATTACH,res=0x1) 000e:Starting thread (entryproc=0x7bfadd10) 000d:Ret PE DLL (proc=0x7afbf41a,module=0x7afb0000 L"MFC71.DLL",reason=PROCESS_ATTACH,res=0x1) retval=1 000d:Call PE DLL (proc=0x7acc31c7,module=0x7acc0000 L"comctl32.dll",reason=PROCESS_ATTACH,res=0x1) ... 000d:Call PE DLL (proc=0x7ab2c803,module=0x7ab00000 L"LIBSTG_EDIT.dll",reason=PROCESS_ATTACH,res=0x1) trace:seh:__regs_RtlRaiseException code=c0000005 flags=0 addr=0xf6850824 trace:seh:__regs_RtlRaiseException info[0]=00000000 trace:seh:__regs_RtlRaiseException info[1]=f6850824 trace:seh:__regs_RtlRaiseException eax=ffffffff ebx=7946ffbc ecx=7946ffbc edx=797d0288 esi=00000001 edi=00000004 trace:seh:__regs_RtlRaiseException ebp=00000001 esp=7ba9fcb8 cs=0073 ds=007b es=007b fs=003b gs=0033 flags=00010202 trace:seh:EXC_CallHandler calling handler at 0x7ab2eafd code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7ab2eb32 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7ab2c4d0 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7bb334a0 code=c0000005 flags=0 wine: Unhandled exception (thread 000d), starting debugger... trace:seh:start_debugger Starting debugger "z:/spare/bon/wine/wine/programs/winedbg/winedbg --auto 12 300" fixme:process:CreateProcessW app (null) cmdline L"z:/spare/bon/wine/wine/programs/winedbg/winedbg --auto 12 300" No process loaded, cannot execute 'c' Wine-dbg>err:winedbg:main Invalid event handle: 0x12c No process loaded, cannot execute 'c' No time to investigate further at the moment. Let me know. if you need more information. Cheers -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Aug. 3, 2005

Re: test case demonstrating PeekMessage give up timeslices

by Alexandre Julliard

Jeremy White <jwhite(a)codeweavers.com> writes: > However, this makes it clear to me that the yield > in message.c is largely moot; you need to remove both > that one and the one in ntdll/sync.c to have > any material effect on Wine timing with messages. Actually it should be enough to not yield in MsgWaitForMultipleObjects when we are only checking for X events, and that would be correct IMO since the check for X events is always in addition to the normal behavior. Something like this should do it: Index: dlls/x11drv/event.c =================================================================== RCS file: /opt/cvs-commit/wine/dlls/x11drv/event.c,v retrieving revision 1.56 diff -u -p -r1.56 event.c --- dlls/x11drv/event.c 25 Jul 2005 11:08:43 -0000 1.56 +++ dlls/x11drv/event.c 3 Aug 2005 08:28:52 -0000 @@ -295,12 +295,13 @@ DWORD X11DRV_MsgWaitForMultipleObjectsEx data->process_event_count++; if (process_events( data->display, mask )) ret = count; - else + else if (count || timeout) { ret = WaitForMultipleObjectsEx( count+1, new_handles, flags & MWMO_WAITALL, timeout, flags & MWMO_ALERTABLE ); if (ret == count) process_events( data->display, mask ); } + else ret = WAIT_TIMEOUT; data->process_event_count--; return ret; } -- Alexandre Julliard julliard(a)winehq.org

Aug. 3, 2005