May 2004 - Wine-Devel - list.winehq.org

great improvements!
by Marius Andreiana May 23, 2004

May 23, 2004

Hi I've been using wine for a long time (without any MS Windows dll). I've upgraded it to the latest version rpm once I installed Fedora Core 2 and I've happily noted these improvements: * /etc/wine for global config options * automatic creation of ~/.wine (drives, C:) There are still some fedora core issues, already in bugzilla. As the roadmap says, would be nice to have stable releases which focus on running by default (without any tweaks) common software, such as IE and Photoshop. (like crossweaver office) Thanks! -- Marius Andreiana Galuna - Solutii Linux in Romania http://www.galuna.ro

1 0

Unhandled exception
by RT May 23, 2004

May 23, 2004

I received the below message on FreeBSD 5.2.1-RELEASE, Wine 20040505 while playing Total Annihilation (non-demo). err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x0 #0 wine_get_thread_data () at pthread.c:534 534 return NtCurrentTeb()->pthread_data; (gdb) backtrace #0 wine_get_thread_data () at pthread.c:534 #1 0x00111e09 in __pthread_thread_self () at kthread.c:106 #2 0x00111e38 in __errno_location () at kthread.c:121 #3 0x00111e48 in __error () at kthread.c:124 #4 0x2020e406 in .cerror () from /lib/libc.so.5 #5 0x00111f19 in cleanup_thread () at kthread.c:198 -- Rod Taylor <rbt [at] rbt [dot] ca> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL PGP Key: http://www.rbt.ca/signature.asc

1 0

Re: Building wine on darwin (resend) (3/6)
by Alexandre Julliard May 22, 2004

May 22, 2004

emmanuel maillard <e.rsz(a)libertysurf.fr> writes: > changelog > Add darwin/ppc support in THREAD_InitStack I'm not sure what the problem is, but the fix doesn't look right at all. Tib.StackBase should point to the base of the stack as it has been allocated, no matter how it's used later on. Most likely you need to fix wine_switch_to_stack or something like that. -- Alexandre Julliard julliard(a)winehq.org

4 4

Fwd: TGMarlett
by David Hammerton May 22, 2004

May 22, 2004

Thanks Steven, However - just a thought here.. Do we want to simply work with the '.ttf' file, or should we keep the 'source' in CVS also? The 'source' file is a '.sfd' file created with PfaEdit [http://pfaedit.sourceforge.net/oldindex.html] now called FontForge [http://fontforge.sourceforge.net/] I'm not really familiar with what extra data the '.sfd' file may have compared to the '.ttf' that may be useful. Is anyone familiar with this stuff? Is the '.sfd' pretty much useless when we have the '.ttf'? Either way, both can be found here (although the '.ttf' Steven sent is probably better, as it contains those fixes he mentions): http://craz.net/files/ Cheers, David Begin forwarded message: > From: Steven Edwards <steven_ed4153(a)yahoo.com> > Date: May 19, 2004 9:21:18 AM GMT+10:00 > To: wine-patches(a)winehq.com > Subject: TGMarlett > Reply-To: wine-devel(a)winehq.org > > Hello, > This is a update to the Marlett replacement developed by TransGamming. > It is needed to get Steam working on Wine. Sylvain Petreolle has hacked > it a bit so it will now load on Windows as well as ReactOS and Linux > with FreeType. The older TGMarlett did not work properly on WindowsXP. > > Thanks > Steven > > > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! - Internet access at a great low price. > http://promo.yahoo.com/sbc/ > -- David Hammerton david(a)craz.net http://crazney.net/ Welfare *NOT* Warfare

1 0

symbol hiding - with gcc -fvisibility
by Guido Draheim May 21, 2004

May 21, 2004

sorry, just saw the note on WWN. I did hope that there would be someone to point to the gcc visibility stuff already - but it seems that people are more concerned to exchange their believes and politics rather showing off some engineering stuff. * preface: it's not in the file format - it's in the tools. The name ELF stands for Extensible Linker Format, it allows to invent all kind of new sections, and expand the symbol table with many interesting attributes that can be checked up by a toolchain. Well, "IF" the tools check for them. * gcc -fvisibility The gcc -fvisibility exists since 3.1 and is supported by binutils. If you read up some web reports, it seems to have been invented for hiding stuff not quite unlike what the original poster wanted. The icc supports all -fvisibility options as well afair. * the real problem traditionally, one can kill local systems which are usable within one file only, i.e. "static". Pretty 20year old unix stuff. The other symbols are referencable outside (in .o) and the standard shard linker will put all of them into the shared library symbol export table. - But now we want two different symbol flavours, one exported to the same library, the others for the rest of the world. Perhaps use a linker script to decide later about symbol visibility. * example solution gcc supports the universal attribute syntax, and it does now know about more symbol flavours as to their visibility. Probably you want to have "hidden". Attached are two simple test*.c files and a makefile. The final sharedlib symbol table contains only test3 after stripping. - using a linker script instead of in-source __attribute__ is left as an excercise to the reader. * more hints search freshmeat - there are ELF tools to staticlink, to obfuscate, and more. It's all in the tools. There is only one problem with opensource: many programmers do not need to hide symbols to the extreme, so they did not write such tools so far. Not yet. There are some real ELF-educated people out there - hire one, and let him write the tool you need. The ELF format is well-defined and simple enough to allow everything and quite easily. Do ut des. -- cheers, guido http://google.de/search?q=guidod extern void test2(void); void __attribute__((visibility("hidden"))) test1(void) { test2(); //__attribute__((visiblity("internal"))) } extern void test1(void); void __attribute__((visibility("hidden"))) test2(void) { test1(); } void test3(void) { test2(); } test.so : test1.c test2.c Makefile gcc -Wl,-x -shared -o $@ test1.c test2.c strip -x $@ objdump -t $@ | grep "test[123]" gcc -Wl,-x -shared -o test.so test1.c test2.c strip -x test.so objdump -t test.so | grep "test[123]" 00000631 g F .text 0000000d test3

3 3

WINE filesystem idea
by Jonathan Wilson May 21, 2004

May 21, 2004

Basicly, when emulated windows version is set to NT4, 2000, XP or 2003, WINE should pretend to apps that its running on NTFS. If running as 95,98 or ME, it should pretend to apps that its running on FAT32. Or better yet, add an option for this (with my suggestions being the default) Just an idea :)

2 1

Wine on AMD64 (heap problem)
by Maurizio Monge May 21, 2004

May 21, 2004

Hello, i compiled wine cvs on my amd64 without many problem (i had to set PATH to point to a directory with wrappers for gcc,ld and as that would call respectively "gcc -m32","ld -melf_i386","as --32", it would be nice if wine would support natively this or would support LDFLAGS=-melf_i368.., but this is not the point). When i started wine i got: wine: failed to create the process heap The same wine executable was running ok on my 32bits distro. I read that this happens on fedora2 too because of nx stack, and i think that, even if i do not have SeLinux installed, the stack is not executable by default on amd64... Do you have any idea of how this could be fixed/hacked? Thanx Maurizio I am not subscribed to wine-devel, so please CC monge(at)sns(dot)it

4 7

Regression with Blizzard patching software
by Aneurin Price May 21, 2004

May 21, 2004

I recently discovered that the software used by Blizzard to patch Diablo 2 and Warcraft 3 (and possibly the same version used with other games), has stopped working. It starts do do something, but before actually applying the patch it crashes out, with the final error message being: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x408ba2e0). In 32-bit mode. 0x408ba2e0 (DIALOG_CreateIndirect+0x300 [dialog.c:636] in USER32.DLL): movl $0x0,0x0(%eax) 139 return TRUE; Wine-dbg>WineDbg terminated on pid a The whole of the scrollback buffer is filled with the usual messages about loading debug information. I could run it with script to see what's happening before that, but I don't think it's really necessary: Since this *used* to work, I've gone through some CVS regression testing and determined that it stopped working sometime between 2004-04-19 22:00:00 and 2004-04-19 22:03:00 CST, so I'm willing to bet that this is what changed: http://www.winehq.org/hypermail/wine-cvs/2004/04/0272.html Since I have no understanding of what's going on here I really coudn't suggest a fix, but I'm happy to provide any further information I can and thought this would be worth pointing out. Aneurin Price

4 3

Re: loader fix for dbghelp
by Alexandre Julliard May 20, 2004

May 20, 2004

Eric Pouech <pouech-eric(a)wanadoo.fr> writes: > I fixed that by sending (in ntdll loader code) the DLL load event a > bit later in the loading processus, when we're out of the dlopen call. This will break dlls that are loading implicitly by ELF loading. That stuff really has to be done in the constructor. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Empty (Stubs in spec only) d3drm
by Ivan Leo Murray-Smith May 20, 2004

May 20, 2004

What app do you know about that uses this dll and works with the native version? All the DX7SDK samples fail with the native version. Ivan.

1 0