March 2005 - Wine-devel - list.winehq.org

vartest.c - major pain in the build process
by Krzysztof Foltman 02 Mar '05

02 Mar '05

Is there any reason for gcc 3.3.1 to spend several minutes on compiling dlls/oleaut32/tests/vartest.c ? I guess it can be explained by optimization stage going nuts on compiling long functions with many branches (contained in the macros), but there must be a way to speed this up. It's barely tolerable now, and upgrading gcc is not an option for everyone. Krzysztof

9 23

user/tests/sysparams.c : test_SPI_SETKEYBOARDPREF on win98
by Paul Vriens 02 Mar '05

02 Mar '05

Hi, I saw this test was recently added. It fails partly on my win98 box as this registry has the values in a different place. WinXP: [HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Preference] "On"="0" Win98: [HKEY_CURRENT_USER\Control Panel\Accessibility] "Keyboard Preference"="0" What's the best(tm) way to cater for both? Just use: SPI_SETKEYBOARDPREF_REGKEY and SPI_SETKEYBOARDPREF_WIN98_REGKEY for example and have the test check the windows version? Or change test_reg_key to cope with 2 different sets? Cheers, Paul.

1 0

Re: Dump HeapWalk entries
by Dimitrie O. Paun 02 Mar '05

02 Mar '05

On Wed, Mar 02, 2005 at 05:52:45PM +0100, Uwe Bonnes wrote: > + if ((entry->wFlags & PROCESS_HEAP_ENTRY_BUSY ) > + && (entry->wFlags & PROCESS_HEAP_ENTRY_MOVEABLE)) > + { > + /* Treat as block */ > + DPRINTF( "BLOCK->hMem\t\t:%08lx\n", (DWORD)entry->u.Block.hMem); > + } Please don't introduce _another_ style of brackets, just use the one that's used in the file. Should be either: if (....) { .... } or if (....) { .... } -- Dimi.

1 0

DPLAYX_ConstructData error during tools/wineinstall
by Paul Vriens 02 Mar '05

02 Mar '05

Hi, I don't know when it started and if found I wasn't able to reproduce, but this is the message I sometimes get during a tools/wineinstall on a clean cvs install: Configuring Wine for a no-windows install in /data/wine-c... err:dplay:DPLAYX_ConstructData : unable to map static data into process memory space (487) /home/paul/.wine updated successfully. I can only say that I noticed this the last few (3?) weeks or so and haven't before. The first time I saw it, I did some regression testing, but as said, I wasn't able to reproduce at will. Is this a problem or can it be ignored (although it's an err). Or better yet, what could be the cause. Cheers, Paul.

1 0

CVS SERVER OUT OF SPACE?
by Oliver Stieber 02 Mar '05

02 Mar '05

Hi, It looks like cvs server has run out of diskspace. cvs update reports. cvs server: Updating . cvs server: failed to create lock directory for `/home/wine/wine' (/home/wine/wine/#cvs.lock): No space left on device cvs server: failed to obtain dir lock in repository `/home/wine/wine' cvs [server aborted]: read lock failed - giving up Send instant messages to your online friends http://uk.messenger.yahoo.com

4 5

Re: [winedbg] Get expressions working again.
by Pouech Eric DMI AEI CAEN 02 Mar '05

02 Mar '05

I don't think this patch should go in as it is: - I don't think it's a good idea to have two ways to express a pointer type in the debugger (one being the standard dbghelp's SymTagPointerType, the other one the new deref count you've introduced). It would be better to add dynamic winedbg types (in the contrary to the static one's we already use dbg_itype_*), when we cannot find one in a module. - the returned string (for internal types' name) should be HeapAllocate:d, not a static buffer - please, use the current style for parenthesis, braces... and don't add a new one A+ > Message du 01/03/05 18:28 > De : "Oliver Stieber" > A : wine-patches(a)winehq.com > Copie à : > Objet : [winedbg] Get expressions working again. > > Hi, > This patch starts to get expressions working again and > also allows derefrencing where there is no explicit > type for that dereference. e.g. > > (short)0x12356 now returns the correct value instead > of an error > > *((int *)0x23467) is now a valid expression. > and > ***((int ***)0x23467) should also work properly. > > This should also fix watches with expressions but I > haven't given it much testing. > > Send instant messages to your online friends http://uk.messenger.yahoo.com > > [ winedbg_expressions_os_1.patch (18.4 Ko) ]

2 1

Re: Add all MIME types
by Mike Hearn 02 Mar '05

02 Mar '05

Scott Ritchie wrote: > -MimeType=application/x-ms-dos-executable > +MimeType=application/x-ms-dos-executable;application/x-msdos-program;application/x-msdownload;application/exe;application/x-exe;application/dos-exe;vms/exe;application/x-winexe;application/msdos-windows;application/x-msdos-program;application/x-zip-compressed > NoDisplay=true Oh my god, there are a lot of these! Wouldn't it be a better long term solution to just get the desktop environments sorted out? They should be sharing the same MIME database now right? So why are they not all identifying EXEs as the same MIME type? thanks -mike

1 0

Re: Ignore msi/version.res
by Alexandre Julliard 02 Mar '05

02 Mar '05

Francois Gouget <fgouget(a)codeweavers.com> writes: > Francois Gouget <fgouget(a)codeweavers.com> > Ignore version.res. version.res is no longer generated. -- Alexandre Julliard julliard(a)winehq.org

1 0

Help with winebuild/winegcc
by Ivan Leo Puoti 02 Mar '05

02 Mar '05

Hello, I'm trying to get a program in the programs/ directory to export symbols, I've added -shared path/to/spec/spec.c to the linker command, but I now get a segmentation fault at startup. Can someone knowledgeable about winegcc/winebuild give me a suggestion/solution? I'm really stuck because of this and can't get on with safedisc support. Ivan.

2 2

re: gcov and Wine (was: Re: Wine cabinet.dll FDI Conformace Test Patch)
by Dan Kegel 02 Mar '05

02 Mar '05

Mike Hearn wrote: > By the way, I talked to Alexandre about the GCOV stuff, basically he wants > us to find out why arc profiling borks the preloader. Then the idea is it > can be enabled just using CFLAGS. (You're confusing the UCLA guys with the Harvey Mudd guys, Mike!) Here's what aarvey(a)cs.hmc.edu wrote when he ran into the problem: > make[1]: Entering directory `/home/aarvey/winefromwinehqcvs/wine.patched/loader' > gcc -o wine-preloader -static -nostartfiles -nodefaultlibs -Wl,-Ttext=0x78000000 preloader.o -L../libs/port -lwine_port > preloader.o(.text+0x1929): In function `_GLOBAL__I_wld_startGCOV': > /home/aarvey/winefromwinehqcvs/wine.patched/loader/preloader.c:955: undefined reference to `__bb_init_func' > collect2: ld returned 1 exit status > make[1]: *** [wine-preloader] Error 1 > make[1]: Leaving directory > `/home/aarvey/winefromwinehqcvs/wine.patched/loader' > make: *** [loader] Error 2 > > I can compile the preloader just dandy as long as I get rid of the extra > compile flags (-ftest-coverage and -fprofile-arcs). You could provide a dummy implementation of __bb_init_func in the preloader, but that's uglier IMHO than just not passing those options when compiling the preloader. Mike also asked: > Until that happens though are you generating lcov output anywhere? Not yet, but I'll ask them to start doing periodic LCOV runs and putting them up on the web. I'd like to see this be a regular feature at winehq.org, not sure what the logistics would be. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

2 1