wine-devel December 2002

wine-devel@winehq.org

132 participants
377 discussions

Start a nNew thread

DLL-Loading
by efm.Pieschel＠t-online.de 18 Dec '02

18 Dec '02

Hello, is there any possibility to load a win32-dll from a Linux program? Thank You for Your response. Bye. Martin

1 0

Re: [D3D8 PATCH] d3d8 shaders update - VS2
by Tony Lambregts 18 Dec '02

18 Dec '02

Raphaël Junqueira wrote: [snip] > object->declLength = i + 1; >- object->function = pFunction; > if (NULL != pFunction) { > for (i = 0; 0xFFFFFFFF != pFunction[i]; ++i) ; > object->functionLength = i + 1; > } else { >- object->functionLength = 1; /* no Function defined use fixed function vertex processing */ >+ object->functionLength = 1; // no Function defined use fixed function vertex processing > > <nitpick> C++ style comments are strongly discouraged </nitpick> -- Tony Lambregts

4 4

re: wmc and ElectricFence
by Dan Kegel 18 Dec '02

18 Dec '02

Sure enough, valgrind finds something to complain about: $ cd dlls/kernel $ make messages/winerr_enu.mc.rc LD_LIBRARY_PATH="../../library:../../unicode:$LD_LIBRARY_PATH" valgrind ../../tools/wmc/wmc -i -U -H /dev/null -o messages/winerr_enu.mc.rc messages/winerr_enu.mc ... ==7935== Invalid read of size 4 ==7935== at 0x804B7A4: yyparse (./mcy.y:232) ==7935== by 0x804A4B3: main (wmc.c:256) ==7935== by 0x420158D3: __libc_start_main (in /lib/i686/libc-2.2.93.so) ==7935== by 0x8048E50: (within /home/dank/wine-20021125/tools/wmc/wmc) ==7935== Address 0x4106E5E4 is 8 bytes inside a block of size 24 free'd ==7935== at 0x4015D715: free (vg_clientfuncs.c:182) ==7935== by 0x804B79A: yyparse (./mcy.y:231) ==7935== by 0x804A4B3: main (wmc.c:256) ==7935== by 0x420158D3: __libc_start_main (in /lib/i686/libc-2.2.93.so) Recompiling wmc with -O0 and rerunning, I get ==7970== Invalid read of size 4 ==7970== at 0x804C73E: yyparse (./mcy.y:232) ==7970== by 0x804AA3B: main (wmc.c:256) ==7970== by 0x420158D3: __libc_start_main (in /lib/i686/libc-2.2.93.so) ==7970== by 0x8048D6C: (within /home/dank/wine-20021125/tools/wmc/wmc) ==7970== Address 0x4106E5E4 is 8 bytes inside a block of size 24 free'd ==7970== at 0x4015D715: free (vg_clientfuncs.c:182) ==7970== by 0x804D2F4: do_add_token (./mcy.y:434) ==7970== by 0x804C731: yyparse (./mcy.y:231) ==7970== by 0x804AA3B: main (wmc.c:256) Looking at y.tab.c, I see the bug is that do_add_token sometimes frees its 2nd argument, which trips up the following line sometimes. Here's the sequence that crashed: do_add_token(tok_language, yyvsp[-6].tok, "language"); if(!find_language(yyvsp[-6].tok->token) && !find_cpxlat(yyvsp[-6].tok->token)) These come from mcy.y: do_add_token(tok_language, $1, "language"); if(!find_language($1->token) && !find_cpxlat($1->token)) Can someone who knows wmc have a look? - Dan

2 1

critical section timeout for the dsound_test
by Enrico Horn 18 Dec '02

18 Dec '02

Hi, Should this happen? ../../../tools/runtest -q -P wine -M dsound.dll -T ../../.. -p dsound_test.exe.so dsound.c && touch dsound.ok fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403bab28,00010020,2):stub fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403bab28,00010020,2):stub err:ntdll:RtlpWaitForCriticalSection section 0x400e40e4 "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) tid=080ddc30 wine: Unhandled exception, starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x400e40e4 "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) tid=080ddc30 err:seh:EXC_DefaultHandling Unhandled exception code c0000194 flags 0 addr 0x400b3ce4 Wine is from CVS just updated this morning. make test will continue despite these errors. Have fun Farmboy farmboy1(a)subdimension.com

2 1

COM conformance test suite?
by Dan Kegel 18 Dec '02

18 Dec '02

Now that the Wine regression tests are starting to shape up, and people are starting to be able to run Visual Basic apps, maybe it's time for us to start thinking about getting ahold of the COM conformance test suite the Open Group did as a companion for their ActiveX standard definition. The Open Group was willing to discuss this, but last time I checked, they wanted to know what was in it for them. (Well, they're not the Free Group, after all.) In particular, they thought it might take them a bit of work to separate the conformance test suite out from their "reference implementation" of ActiveX for Unix. Given that attitude, the best strategy is probably to start implementing our own test suite for the APIs in question, and shame them into opening theirs :-) For those who haven't seen it yet, the Open Group's ActiveX spec (http://www.opengroup.org/onlinepubs/009899899/ ) is perhaps the only document defining Win32 API calls in a standards-body-like-way. (The Tru64 Unix doc, http://www.tru64unix.compaq.com/com/documentation/building/ contains some related material. Might be worth archiving this before it goes offline as HP discontinues Tru64 Unix.) The Open Group spec only covers a little bit of Win32, but it sure looks like a useful bit. The #include files it seems to define are: #include <comcat.h> #include <oaidl.h> #include <objbase.h> #include <objidl.h> #include <ocidl.h> #include <ole2.h> #include <oleauto.h> #include <olectl.h> #include <oleidl.h> #include <unknwn.h> #include <urlmon.h> #include <winerror.h> #include <winnls.h> #include <winreg.h> which is a fair chunk. - Dan p.s. My cat is helping test mozilla 1.3alpha. She discovered just now that running across the keyboard causes that app to abort with sig 11...

1 0

wmc and ElectricFence
by Sylvain Petreolle 18 Dec '02

18 Dec '02

Looking for memleaks in wine, I tried to compile the current CVS and link with ElectricFence. I did LDFLAGS=-lefence ./configure. Running make in dlls/kernel detects a problem in wmc (hope its not in ElectricFence ;)): make[2]: Entre dans le répertoire `/home/wine/dlls/kernel' LD_LIBRARY_PATH="../../library:../../unicode:$LD_LIBRARY_PATH" ../../tools/wmc/wmc -i -U -H /dev/null -o messages/winerr_enu.mc.rc messages/winerr_enu.mc Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens <bruce(a)perens.com> messages/winerr_enu.mc:19: Oops, segment violation make[2]: *** [messages/winerr_enu.mc.rc] Abandon make[2]: Quitte le répertoire `/home/wine/dlls/kernel' make[1]: *** [kernel] Erreur 2 make[1]: Quitte le répertoire `/home/wine/dlls' make: *** [dlls] Erreur 2 ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

running cygwin apps(gcc etc.) under wine
by chrismorgan＠rcn.com 18 Dec '02

18 Dec '02

Trying to run my work related code build process under wine results in some failures with cygwin's gcc. Even with a simple hello world.c file and 'gcc -o test test.c' I get: 0 [main] gcc -134958416 sync_with_child: child 134963016(0xB0) died before initialization with status code 0x1 2599 [main] gcc -134958416 sync_with_child: *** child state waiting for longjmp 1335488 [main] gcc -134958416 sync_with_child: child 134968376(0xC0) died before initialization with status code 0x1 1337536 [main] gcc -134958416 sync_with_child: *** child state waiting for longjmp 3711485 [main] gcc -134958416 sync_with_child: child 134969736(0xD0) died before initialization with status code 0x1 3713593 [main] gcc -134958416 sync_with_child: *** child state waiting for longjmp 8125556 [main] gcc -134958416 sync_with_child: child 134970152(0xE0) died before initialization with status code 0x1 8127752 [main] gcc -134958416 sync_with_child: *** child state waiting for longjmp gcc: vfork: Resource temporarily unavailable Any ideas why this is occuring? Is this due to issues with pthreads? Thanks, Chris

5 5

Re: wineboot - adapting to wine build env
by Matthew Davison 18 Dec '02

18 Dec '02

On Tue, 2002-12-17 at 19:23, Shachar Shemesh wrote: > If anyone did not understand, my previous post was with Andy's > implementation of wineboot. This post is with the changes to the rest of > Wine to make wineboot fit in better. > > Also - my previous patch included a Makefile file by mistake. Please > ignore and sorry for the noise. > > Changelog: > Shachar Shemesh <winecode(a)sun.consumer.org.il> > > * Add wineboot to the makefiles so it will compile > * Add wineboot's configs to the default config file > > I have some work to the RunOnceEx section of wineboot, once (and if) Andy's version is commited will send a patch. (the work involves a couple of bugfixes and some work on the rundll type calls(ones with | symbols)) > > ______________________________________________________________________ > > Index: configure.ac > =================================================================== > RCS file: /home/sun/sources/cvs/wine/configure.ac,v > retrieving revision 1.112 > diff -u -r1.112 configure.ac > --- configure.ac 17 Dec 2002 01:49:17 -0000 1.112 > +++ configure.ac 17 Dec 2002 17:57:55 -0000 > @@ -1494,6 +1494,7 @@ > programs/uninstaller/Makefile > programs/view/Makefile > programs/wcmd/Makefile > +programs/wineboot/Makefile > programs/wineconsole/Makefile > programs/winedbg/Makefile > programs/winefile/Makefile > Index: documentation/samples/config > =================================================================== > RCS file: /home/sun/sources/cvs/wine/documentation/samples/config,v > retrieving revision 1.37 > diff -u -r1.37 config > --- documentation/samples/config 13 Dec 2002 02:26:18 -0000 1.37 > +++ documentation/samples/config 17 Dec 2002 18:51:49 -0000 > @@ -67,6 +67,29 @@ > ;"ShowDotFiles" = "1" > "ShellLinker" = "wineshelllink" > > +[wineboot] > +"BootConfig_Enable" = "1" > +# do a dry run, i.e. show what to do, but don't act > +"BootConfig_DryRun" = "0" > +# extra verbosity on console > +"BootConfig_TTY_Verbose" = "0" > +# extra quiet on console > +"BootConfig_TTY_Quiet" = "0" > +# process wininit.ini ? > +"WininitIni_Execute" = "1" > +"RunServicesOnce_Execute" = "1" > +"RunServicesHKLM_Execute" = "1" > +"RenameFiles_Execute" = "1" > +"RunOnceHKLM_Execute" = "1" > +"RunOnceEx_Execute" = "1" > +"WinIniLoad_Execute" = "1" > +"WinIniRun_Execute" = "1" > +"RunHKLM_Execute" = "1" > +"RunHKCU_Execute" = "1" > +"StartupFolderCommon_Execute" = "1" > +"StartupFolderUser_Execute" = "1" > +"RunOnceHKCU_Execute" = "1" > + > # <wineconf> > > [Version] > Index: programs/Makefile.in > =================================================================== > RCS file: /home/sun/sources/cvs/wine/programs/Makefile.in,v > retrieving revision 1.32 > diff -u -r1.32 Makefile.in > --- programs/Makefile.in 2 Dec 2002 21:17:05 -0000 1.32 > +++ programs/Makefile.in 17 Dec 2002 17:57:08 -0000 > @@ -22,6 +22,7 @@ > uninstaller \ > view \ > wcmd \ > + wineboot \ > wineconsole \ > winedbg \ > winefile \ -- Matthew Davison <m.davison(a)virgin.net>

2 1

Re: Documentation cleanup for Relay|Snoop-Include|Exclude
by Dmitry Timoshkov 18 Dec '02

18 Dec '02

"Uwe Bonnes" <bon(a)elektron.ikp.physik.tu-darmstadt.de> wrote: > +.I --debugmsg -relay > +will turn on all relay messages. For more control on including or excluding > +functions and dlls look into the [Debug] section of the wine configuration file. Shouldn't it be '+relay'? -- Dmitry.

1 0

windows visual view ?
by Tom Wickline 18 Dec '02

18 Dec '02

Is was just wondering if there was any type of Windows visaul view ? view as in how evreything is layed out ? and how wine compares to Win32 ? Say if you had a visual view of how win32 is layed out and just how close wine comes to this . If there was a negitive of Win-ME for example and one of wine how would wine look if it was layed on top of the Win-ME negitive ? I am trying to view Win32 in my head and wine and how they ( scope ) up..... could this cause a brain hemorrhage ?? ......... :) comments , flames , views, insight most welcome Tom

3 3

← Newer
1
...
11
12
13
14
15
16
17
...
38
Older →

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 December 2002