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

Re: Mac OS X Support : Asm syntax support [Fixed]

by Alexandre Julliard

"Pierre d'Herbemont" <stegefin(a)free.fr> writes: > +# define LD_SKIP(i) This won't work, we need to reserve space for the PE header. > +# define PPC_SYM(sym_name) "_" #sym_name This one should use __ASM_NAME. Also it would be nice if you could use fewer macros, this makes the code quite ugly. It seems the main difference is in register names, you could simply have one macro for that and leave the rest alone. -- Alexandre Julliard julliard(a)winehq.com

June 27, 2003

imagehlp.h question - building with Mingw or MS_VC headers

by Steven Edwards

around line 560 in imagehlp.h we have this /*********************************************************************** * Wine specific */ extern HANDLE IMAGEHLP_hHeap; Can this be moved to a internal header or done in some other way so we can build with other headers? Thanks Steven

June 27, 2003

Re: RFC: dsound patch

by Robert Reif

I just sent a rather large patch to wine-patches that addresses a number of 3D sound problems and also fixes a problem I was having when switching between sound cards quickly. I added more tests for 3D, COM and reference counts and have run the tests on win2k with dx8.1 with the same results. I have also tested with the sample programs from the DX8 SDK. Please test it with real apps and send me feedback. Thanks, Bob.

June 27, 2003

Official MS symbol sets

by Mike Hearn

Hi, http://www.microsoft.com/whdc/ddk/debugging/symbolpkg.mspx I assume people have looked at this before - how easy are they to match up with Wine, and do people use them for debugging faults in native code? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

June 27, 2003

Re: Wine Status Changelog

by Tom

Robert North wrote: > > Is this in the CVS tree? > Can't see it on the cvsweb page > or in the repository. I would like to apologize for any misunderstandings about my post on the Wine Status changelog. To clarify the Changelog that i'm working on is the Wine Status Page Changelog and it can be found here: http://www.winehq.com/?page=status_changelog I will add Robert North as a worker for Wintab32. And since the patch from Aric has not been commit'd to CVS the status that I have at this time has to be far to high. So if there are no objections I will place the current status at 25% and when the patches from Aric and Robert are commit'd I will then raise the status to what they see as being appropriate. -Thanks Tom > > > Cheers > -Rob. > > >

June 27, 2003

[Patch] dlls/oleaut32/typelib.c - Via a CVS search, reverse regression to get Kazza working

by Stefan Jones

On upgrading to Wine 20030618 I found that kazaa lite will no longer work and gave me the following error: No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHDOCVW.DLL' (0x71000000) Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x411ed9c9). In 32-bit mode. 0x411ed9c9 (ITypeInfo_fnGetContainingTypeLib+0x49 [typelib.c:4801] in oleaut32.dll.so): call *0x4(%edx) 4802 TRACE("returning ppTLib=%p", *ppTLib); Wine-dbg>WineDbg terminated on pid a using in wine.config: [AppDefaults\\KazaaLite.kpp\\DllOverrides] "*" = "builtin, native, so" ;"shdoclc" = "native" "shdocvw" = "native" "shlwapi" = "native" "commctrl" = "native" ;"comdlg32" = "native" I looked though the CVS logs and mail archives and I found the following: http://www.winehq.org/hypermail/wine-devel/2003/06/0414.html and the patch below which was applied to dlls/oleaut32/typelib.c This caused the crash, reversing it fixes the error. please fix / apply, or I will cry!!! anyway, how do you use winedbg, I am not thick but it refuses to do normal gdb stuff like the run command or a backtrace! Is there a URL I missed? Stefan revision 1.95 date: 2003/05/13 22:15:26; author: julliard; state: Exp; lines: +0 -2 Dmitry Timoshkov <dmitry(a)codeweavers.com> Remove redundant ITypeLib2_AddRef's. Makes LoadTypeLib/ITypeLib2_Release work. Index: typelib.c =================================================================== RCS file: /home/wine/wine/dlls/oleaut32/typelib.c,v retrieving revision 1.94 retrieving revision 1.95 diff -u -r1.94 -r1.95 --- typelib.c 13 May 2003 00:41:58 -0000 1.94 +++ typelib.c 13 May 2003 22:15:26 -0000 1.95 @@ -1844,7 +1844,6 @@ pcx->pTblDir->pTypeInfoTab.offset+count*sizeof(tiBase)); /* this is where we are coming from */ ptiRet->pTypeLib = pLibInfo; - ITypeLib2_AddRef((ITypeLib2 *)pLibInfo); ptiRet->index=count; /* fill in the typeattr fields */ FIXME("Assign constructor/destructor memid\n"); @@ -3055,7 +3054,6 @@ } *ppTypeInfoImpl = (ITypeInfoImpl*)ITypeInfo_Constructor(); (*ppTypeInfoImpl)->pTypeLib = pTypeLibImpl; - ITypeLib2_AddRef((ITypeLib2 *)pTypeLibImpl); (*ppTypeInfoImpl)->index = i; (*ppTypeInfoImpl)->Name = TLB_MultiByteToBSTR( pOtherTypeInfoBlks[i].name_offs +

June 26, 2003

Re: Doom Legacy / Problems with DOS & and winedbg

by Eric Pouech

Sylvain Petreolle wrote: >>you shouldn't need to change the mode, why do you want to switch to >>mode >>32 ? > > since it complains in vm86 mode, I tried something different (all the > others :)) > > >>since the pc has changed between the two exceptions, I assume several >>int 21 take place in a row. > > yes, this is a dos prog... wich makes use of the long filename > functions of win95. > > >>so, if you use cont at the second exception, you're stuck as for the >>first one. So, you should use pass if you want the execution to be >>correct (even the second time) > > this is why I tried to switch to mode 16/32, to have no more problem > (do you know how many int calls are made in a dos prog ? ;) in that case, you can use a different technique. Add a DebugBreak(); call in the offending function, and run the program without the wine debugger. The first time the offending func will be used, the debugger will be opened (if this lets you go further without passing all the time) As of today, there's no automated way of passing N times, nor ignoring a given exception (we could add what gdb does: a mapping of behavior between a given exception (signal in gdb) and the behavior: enter debugger, pass exception, continue, exit...) A+ -- Eric Pouech

June 26, 2003

Re: Doom Legacy / Problems with DOS & and winedbg

by Sylvain Petreolle

> you shouldn't need to change the mode, why do you want to switch to > mode > 32 ? since it complains in vm86 mode, I tried something different (all the others :)) > since the pc has changed between the two exceptions, I assume several > int 21 take place in a row. yes, this is a dos prog... wich makes use of the long filename functions of win95. > so, if you use cont at the second exception, you're stuck as for the > first one. So, you should use pass if you want the execution to be > correct (even the second time) this is why I tried to switch to mode 16/32, to have no more problem (do you know how many int calls are made in a dos prog ? ;) ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

June 26, 2003

Re: Doom Legacy / Problems with DOS & and winedbg

by Eric Pouech

Sylvain Petreolle wrote: >>>Unfortunately, winedbg complains on the first int21 call : >>>First chance exception: interrupt 21 in vm86 mode in vm86 code >>>(00d4:045e). >>> >>>How can this be avoided ? >> >>do you get the winedbg prompt or not ? if so, 'pass' should do. > > This works, thanks. But the same error appears on the next interrupt > call. > > I tried 'mode 16' and 'mode 32' but they seem to do nothing. > I stay in vm86 mode. you shouldn't need to change the mode, why do you want to switch to mode 32 ? since the pc has changed between the two exceptions, I assume several int 21 take place in a row. so, if you use cont at the second exception, you're stuck as for the first one. So, you should use pass if you want the execution to be correct (even the second time) A+ -- Eric Pouech

June 26, 2003

Re: Doom Legacy / Problems with DOS & and winedbg

by Sylvain Petreolle

> > Unfortunately, winedbg complains on the first int21 call : > > First chance exception: interrupt 21 in vm86 mode in vm86 code > > (00d4:045e). > > > > How can this be avoided ? > > do you get the winedbg prompt or not ? if so, 'pass' should do. This works, thanks. But the same error appears on the next interrupt call. I tried 'mode 16' and 'mode 32' but they seem to do nothing. I stay in vm86 mode. First chance exception: interrupt 21 in vm86 mode in vm86 code (00d4:0063). In vm86 mode. Register dump: CS:00d4 SS:00d4 DS:00d4 ES:00c4 FS:0000 GS:0000 IP:0063 SP:0760 BP:0000 FLAGS:0202( - 00 I - - 1 ) AX:3000 BX:0000 CX:0000 DX:0000 SI:0000 DI:0000 Stack dump: 0x00d4:0x0760: 00c4 0000 0000 0000 0000 0000 0000 0000 0x00d4:0x0770: 0000 0000 0000 0000 0000 0000 0000 0000 0x00d4:0x0780: 0000 0000 0000 0000 0000 0000 0000 0000 0x00d4:0x0790: Backtrace: =>0 0x00d4:0x0063 (bp=0000) Bad stack frame 0x01f7ffd0 0x00d4:0x0063: cmpb $3,%al Wine-dbg>pass First chance exception: interrupt 21 in vm86 mode in vm86 code (00d4:0093). Register dump: Wine-dbg>mode 16 Wine-dbg>cont First chance exception: interrupt 21 in vm86 mode in vm86 code (00d4:00d7). In vm86 mode. ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

June 26, 2003