June 2003 - Wine-devel - list.winehq.org

Windows 2000 winetest results from source release 20030508
by Josh Metzler 13 Jun '03

13 Jun '03

I retrieved the wine source release of 20030508. I ran ./tools/winapi/msvcmaker --no-wine. Note: I did this in Cygwin, and I had to make some changes to the perl script to get it to run. I also created a wine subdirectory under each of the test subdirs, and copied test.h into it. The MSVC versions couldn't find this file otherwise. Also, I was unable to compile shlwapi_test even after copying unicode.h into the shlwapi/test/wine subdir I had created. I tried to run all the tests that said they needed retested, or that had any errors according to http://fgouget.free.fr/wine/tests-en.shtml. I ran these tests from within MSVC++ 6.0 on a Windows 2000 SP3 machine, and tried to find out what an API returned when it was different from what the test expected. If someone could suggest how the tests should deal with different return values on different Windows versions, and also tell me the best way to create patches, I would be willing to try to help fix some of these tests. Josh Metzler -- kernel32_test locale locale.c:154: Test failed: GetTimeFormat got '' instead of '4' locale.c:155: Test failed: GetTimeFormat: got 1 instead of 2 locale.c:181: Test failed: GetTimeFormat got '8.@:56AM' instead of '8.@:56.@:AM' locale.c:182: Test failed: GetTimeFormat: got 9 instead of 12 locale.c:190: Test failed: GetTimeFormat got '' instead of '3' locale.c:191: Test failed: GetTimeFormat: got 1 instead of 2 locale.c:466: Test failed: GetDateFormat got '5/4/2002' instead of '5/4/02' locale.c:467: Test failed: GetDateFormat: got 9 instead of 7 locale.c:489: Test failed: GetDateFormat check DATE_YEARMONTH with null format expected ERROR_INVALID_FLAGS got return of '10' and error of '0' locale: 112 tests executed, 0 marked as todo, 9 failures. Notes: 489: GetDateFormat returned 10, buffer contained "May, 2002" In other words, the function succeeded. path path.c:514: Test failed: GetLongPathNameA: wrong return code, 97 instead of 42 path.c:881:TMP=C:\DOCUME~1\josh\LOCALS~1\Temp path.c:892:TMP=C:\WINNT path.c:902:TMP=C:\ path.c:912:TMP=C: path: 1730 tests executed, 0 marked as todo, 1 failure. Notes: 514: Counting the characters, the size of the long path name was 96. The function did exactly what the MSDN library said it will do - return the lenght of the buffer necessary to hold the long path name. process tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. process.c:870: Test failed: StartupInfoA:lpDesktop expected (null), got WinSta0\Default process.c:871: Test failed: StartupInfoA:lpTitle expected (null), got C:\cygwin\home\josh\wine\dlls\kernel\tests\Output\Win32_MSVC_Headers\kernel32_test.exe tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. process.c:918: Test failed: StartupInfoA:lpDesktop expected (null), got WinSta0\Default process.c:919: Test failed: StartupInfoA:lpTitle expected (null), got C:\cygwin\home\josh\wine\dlls\kernel\tests\Output\Win32_MSVC_Headers\kernel32_test.exe process: 309 tests executed, 0 marked as todo, 4 failures. Notes: looks like Windows 2000 fills in the window station and title if they are null. I wonder who owns that memory? thread thread: 113 tests executed, 0 marked as todo, 0 failures. /************************************************************************/ netapi32_test access access.c:110: Test failed: Bad Network Path: rc=0 access: 23 tests executed, 0 marked as todo, 1 failure. Notes: NetUserGetInfo succeeds when passed an empty string, getting user info for the local computer. Test expected ERROR_BAD_PATH as the return value. /************************************************************************/ oleaut32_test vartest vartest.c:1761:======== Testing VarUI1FromXXX ======== vartest.c:1849:======== Testing VarUI2FromXXX ======== vartest.c:1936:======== Testing VarUI4FromXXX ======== vartest.c:2022:======== Testing VarI1FromXXX ======== vartest.c:2088:======== Testing VarI2FromXXX ======== vartest.c:2133:======== Testing VarI4FromXXX ======== vartest.c:2177:======== Testing VarR4FromXXX ======== vartest.c:2224:======== Testing VarR8FromXXX ======== vartest.c:2244:======== Testing VarDateFromXXX ======== vartest.c:2315:======== Testing VarBoolFromXXX ======== vartest.c:2371:======== Testing VarBSTRFromXXX ======== vartest.c:2604:======== Testing Hi-Level Variant API ======== vartest.c:2691:======== Testing different VARTYPES ======== vartest: 1875 tests executed, 0 marked as todo, 0 failures. /************************************************************************/ shell32_test shlfileop shlfileop: 121 tests executed, 0 marked as todo, 0 failures. /************************************************************************/ urlmon_test generated generated: 4 tests executed, 0 marked as todo, 0 failures. /************************************************************************/ user32_test sysparams sysparams.c:1112:strict=0 sysparams.c:214:testing SPI_{GET,SET}BEEP sysparams.c:350:testing SPI_{GET,SET}MOUSE sysparams.c:455:testing SPI_{GET,SET}KEYBOARDSPEED sysparams.c:487:testing SPI_ICONHORIZONTALSPACING sysparams.c:530:testing SPI_{GET,SET}SCREENSAVETIMEOUT sysparams.c:564:testing SPI_{GET,SET}SCREENSAVEACTIVE sysparams.c:601:testing SPI_{GET,SET}KEYBOARDDELAY sysparams.c:634:testing SPI_ICONVERTICALSPACING sysparams.c:685:testing SPI_{GET,SET}ICONTITLEWRAP sysparams.c:718:testing SPI_{GET,SET}MENUDROPALIGNMENT sysparams.c:754:testing SPI_{GET,SET}DOUBLECLKWIDTH sysparams.c:785:testing SPI_{GET,SET}DOUBLECLKHEIGHT sysparams.c:817:testing SPI_{GET,SET}DOUBLECLICKTIME sysparams.c:869:testing SPI_{GET,SET}MOUSEBUTTONSWAP sysparams.c:895:testing SPI_GETFASTTASKSWITCH sysparams.c:910:testing SPI_{GET,SET}DRAGFULLWINDOWS sysparams.c:948:testing SPI_{GET,SET}WORKAREA sysparams.c:992:testing SPI_{GET,SET}SHOWSOUNDS sysparams.c:1042:testing SPI_{GET,SET}DESKWALLPAPER sysparams: 412 tests executed, 0 marked as todo, 0 failures. /************************************************************************/ winspool_test info info: 10 tests executed, 0 marked as todo, 0 failures.

1 0

Re: wine-devel digest, Vol 1 #2004 - 15 msgs
by Emmanuel Goldstein 13 Jun '03

13 Jun '03

> On Thu, 12 Jun 2003 20:52:34 +1200, Sir Emmanuel Goldstein scribed thus: > > wIntegrate appears to use an internal, custom implementation of Winsock. > > That is, I cannot see it link winsock when i do -debugmsg +dll. > I doubt that.... the correct channel is +loaddll, try with that. Ok, I've run it with +loaddll. wIntegrate is linking an ActiveX control, wWinsock.ocx. > > -debugmsg +winsock yeilds a little information, but not much. i tried a > > -debugmsg +all, but that filled up my hard disc and caused X to crash. > > What can I do to help further determine the problem? > > Try a +relay trace. For something as vague as this you need to investigate > further really, there is an infinite multitude of things that could be > going wrong. I tried running the program with native dlls. In the end, I wound up with a Winsock error 138. I tried a relay trace, this crashed my X session (before you ask, i'm running debian woody.)

1 0

Re: [xplane] Re: DSound buffer underrun problems with X-Plane
by Christian Neumair 13 Jun '03

13 Jun '03

Am Fre, 2003-06-13 um 08.29 schrieb stationairskyhawk: > --- In xplane(a)yahoogroups.com, Christian Neumair <chris(a)g...> wrote: > > I'm currently testing a cool flight simulator called X-Plane. It's > > really working great on wine, the performance is supersonic. The only > > downer is that the engine sound is a bit staccato, i.e. it has small > > breaks. My non-debug debian wine continuously outputs: > > > > "err:dsound:DSOUND_MixOne underrun on sound buffer 0x4b4c47c8" > > This is a known issue. When x-plane's performance becomes supersonic, it is natural > to expect the sound to drop out. Many have found that by reducing x-plane's > performance to subsonic levels, the sounds returns. I don't think this is the reason. I'm not on a very fast machine, but the sound problems occur independent of my graphic settings. They even are revisable when X-Plane shows its splash screen and loads the last used plane which makes me believe that something goes wrong in wine's sound mixing code. regs, Chris

1 0

Re: Debuging Wine
by Jarmo 13 Jun '03

13 Jun '03

Hi, I am trackin a weard bug and I would need a help a little. I am trying to run Orbiter in winex. Orbiter runs without problems in windows. It seems that Orbiter.exe is using a call that does not exist in wine. How can I find out the name of that call ? access to call 0x406cd420 Main_Direct3DDevice_SetTexture works fine just before this call. Code causing the crash: 0x004513c0 movl %eax,0x4c(%esp) 0x004513c4 call *0x84(%eax) this will lead 0xdead001e Relocation entries: 0x406cd010 is address of Main_Direct3DDevice_DrawIndexedPrimitiveVB 0x406cd3a0 is address of Main_Direct3DDevice_GetTexture 0x406f0910 (DDRAW.DLL): 406cd2f0 406ccae0 406ccc70 406cce60 0x406f0920 (DDRAW.DLL): 406cd010 *! dead001e !* 406cd3a0 406cd420 0x406f0930 (DDRAW.DLL): 406cd530 406cd5f0 406cd700 406cd760 Relocation entries: 0003d91c R_386_32 Main_Direct3DDevice_DrawPrimitiveVB 0003d920 R_386_32 Main_Direct3DDevice_DrawIndexedPrimitiveVB 0003d924 ? ? ? ? 0003d928 R_386_32 Main_Direct3DDevice_GetTexture 0003d92c R_386_32 Main_Direct3DDevice_SetTexture Regards, Jarmo

3 2

SoftICE for wine
by Gerhard W. Gruber 12 Jun '03

12 Jun '03

Three weeks ago I was trying to find a crash in Agent. Since I don't know the code of wine so well I tried to do this with a debugger. My experience was rather frustrating. GDB and winegdb are not exactly what I call userfriendly. On a Windows system I would have found this error within a few hours but I didn't come to terms with winedbg and gdb. So I was looking for an alternative and I found a project on sourceforge named pICE. This project was abandoned about two years ago, but I was interested in it and now I got the administration for it. pICE is a kernel debugger for linux similar to SoftICE and I thought it would be nice to have such a tool. My intention is to add extensions to support wine debugging as well (this was my primary reason) and now I would like to know if this is would be of interest to you as well and if yes (what I hope :) ) what extensions are needed in order to support wine. I guess that winedbg is similar in that respect that it is also an extension of gdb, am I right? If somebody knows the details I would like to hear it. But don't expect anything soon because I still need to dig into the code of pICE to make it stable first. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

3 7

EXC_RtlRaiseException call to unimplemented function kernel32.dll.CreateRemoteThread
by tux＠leahcim.com 12 Jun '03

12 Jun '03

Hi, i've installed the latest cvs rpm ( wine-cvs-unstripped-20030612-1.i386.rpm ) and it seems to work with most applications. however when I try to make the ud agent run it fails with the following exception as soon as the calculation engine attempts to start: (C:\udagent\ud_1706422_0.dir\ud_ligfit_Release.exe,...): [...] fixme:seh:EXC_RtlRaiseException call to unimplemented function kernel32.dll.CreateRemoteThread fixme:msvcrt:_XcptFilter (-2147483392,0x40890a38)semi-stub wine: Unhandled exception, starting debugger... err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 11 84") (2) But according to the Changelog of an older version the CreateRemoteThread thingy has been implemented: * include/winbase.h: Francois Gouget <fgouget(a)codeweavers.com> Added CreateRemoteThread. any ideas ? I'd be grateful for any suggestions. -- Stefan

3 3

Debuging Wine
by Jarmo 12 Jun '03

12 Jun '03

Hi, I am trying to have Orbiter running under winex in Linux. I have plenty of experience in programming but I haven't used much debuggers. I would have few questions. What is the difference between dll load methods "builtin" and "so" when debugging witch one should be used ? When using "so" mode this error is generated. I added "_ftol" in libmsvcrt.so and that error is no longer generated. Is that right thing to do ? When using "builtin" mode these errors won't appear. But it will crash the same way. ---------------------------------------------------------------------------------------------------- fixme:win32:ELF_FindExportedFunction function ftol not found: /usr/local/lib/libwine.so: undefined symbol: ftol err:win32:PE_fixup_imports No implementation for MSVCRT.dll.237(_ftol) imported from C:\Orbit_new\Modules\Luna.dll, setting to 0xdeadbeef fixme:win32:ELF_FindExportedFunction function ??3(a)YAXPAX@Z not found: /usr/local/lib/libwine.so: undefined symbol: ??3 err:win32:PE_fixup_imports No implementation for MSVCRT.dll.16(??3(a)YAXPAX@Z) imported from C:\Orbit_new\Modules\Luna.dll, setting to 0xdeadbeef fixme:win32:ELF_FindExportedFunction function ?terminate@@YAXXZ not found: /usr/local/lib/libwine.so: undefined symbol: ?terminate err:win32:PE_fixup_imports No implementation for MSVCRT.dll.46(?terminate@@YAXXZ) imported from C:\Orbit_new\Modules\Luna.dll, setting to 0xdeadbeef --------------------------------------------------------------------------------------------------- What are these ? No debug information in 32bit DLL 'DDRAW.DLL' (0x406c8000) *** Invalid address 0x40011f80 (_end+0x478) from msvcrt.spec: @ forward -noimport _ftol ntdll._ftol @ cdecl ?terminate@@YAXXZ() MSVCRT_terminate This is the final crash. ------------------------------------------------------------------------------------------------ First chance exception: page fault on read access to 0xdead001e in 32-bit code (0xdead001e). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:2007 GS:0007 EIP:dead001e ESP:406a287c EBP:004b3b88 EFLAGS:00210202( R- 00 I - - 1 ) EAX:406f08a0 EBX:403a62d4 ECX:433c0e10 EDX:433c0e00 ESI:403a62d4 EDI:00000000 Stack dump: 0x406a287c (MSVCRT.DLL.193+0x3f48ec): 004513ca 403a62d4 433c0e00 433c0e10 0x406a288c (MSVCRT.DLL.193+0x3f48fc): 00000001 00000000 433c0e20 406cbdf0 0x406a289c (MSVCRT.DLL.193+0x3f490c): 403a62d4 433fdbc0 406cb900 00000000 0x406a28ac (MSVCRT.DLL.193+0x3f491c): 00000000 00000000 406cb900 00000000 0x406a28bc (MSVCRT.DLL.193+0x3f492c): 00000000 433fdbc0 0047017a 00470185 0x406a28cc (MSVCRT.DLL.193+0x3f493c): 406f08a0 40738820 ff000000 406a2a28 0x406a28dc (MSVCRT.DLL.193+0x3f494c): 0400: sel=2007 base=4011b460 limit=00000000 32-bit rw- Backtrace: =>0 0xdead001e (MSVCRT.DLL._winver+0x99fe36ce) (ebp=004b3b88) 1 0x433c0de0 (MSACM32.DLL.acmStreamUnprepareHeader+0x33d190) (ebp=00000001) 0xdead001e (MSVCRT.DLL._winver+0x99fe36ce): *** Invalid address 0xdead001e (MSVCRT.DLL._winver+0x99fe36ce) -- no code -- ---------------------------------------------------------------------------------------------------- I know very little about this. It seems that processor is trying to execute code in 0xdead001e. That would indicate a missing function. If that what it is. What is the missing function ? Where it shoud be ? What is calling it ? What is "1e" in 0xdead001e I dumped MSACM32.DLL and it does not inport any MSVCRT.DLL functions. acmStreamUnprepareHeader disassembly doesn't show anything weard either. Regards, Jarmo

3 3

Re: quartz once again: was DEVENUM.DLL Implementation
by Brian Vincent (C) 12 Jun '03

12 Jun '03

> By the way, nobody ever knew *why* Hidenori asked to have his code removed. > The fact that it's due to legal issues with the code are only, as far as I > know, rumors. Not true, here's what Hidenori wrote (WWN #122): "My all MultiMedia codes are completely written from scratch. No disassembling. I believe there are no legal issues. But, I cannot warrant... I should protect myself from any potential problems now..." "The main issues for me are 1) restrictions of EULA - some codes may be based on information from non-VS6. I don't want to battle with EULA. 2) afraid to many pending patents. I cannot check all patents... and there are some other reasons I don't want to write..." "So, finally, I decided to solicite Alexandre..." http://www.winehq.com/hypermail/wine-devel/2002/05/0080.html He asked for it to be removed, I think Alexandre is right in not distributing it. I'm not sure Gav ever got permission to redistribute with WineX. The last thing I remember seeing from him was they asked for permission but hadn't received a reply. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

DSound buffer underrun problems with X-Plane
by Christian Neumair 12 Jun '03

12 Jun '03

I'm currently testing a cool flight simulator called X-Plane. It's really working great on wine, the performance is supersonic. The only downer is that the engine sound is a bit staccato, i.e. it has small breaks. My non-debug debian wine continuously outputs: "err:dsound:DSOUND_MixOne underrun on sound buffer 0x4b4c47c8" after reporting once: "fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x4038ac70,00010021,1):stub" I'm not sure how complicated it is to resolve that but I assume for an advanced wine hacker familiar with directx (especially those currently working on it, *hint*, *hint*) it isn't very hard to fix. The problem is reproducible with the current stable version 6.71 and the brand-new 7.0 beta. You can fetch both betas under http://x-plane.com. Thanks in advance! You do a great job! regs, Chris

1 0

Re: Re: wIntegrate vs Wine
by Pouech Eric DMI AEI CAEN 12 Jun '03

12 Jun '03

> > -debugmsg +winsock yeilds a little information, but not much. i tried a > > -debugmsg +all, but that filled up my hard disc and caused X to crash. What > > can I do to help further determine the problem? > > Try a +relay trace. For something as vague as this you need to investigate > further really, there is an infinite multitude of things that could be > going wrong. you can also edit dlls/winsock/socket.c and set DEBUG_SOCK_ADDR to 1, you'll get a bit more of traces A+

1 0