wine-devel November 2003

wine-devel@winehq.org

121 participants
276 discussions

Re: Regressions....
by Marcelo Duarte 24 Nov '03

24 Nov '03

Em Sáb 15 Nov 2003 13:28, você escreveu: Hi, Recently I found plus a regression when trying to install my application, using the installer of the M$, with updated cvs. See the error: [mduarte@mduarte setup]$ wine config Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: err:seh:setup_exception stack overflow 304 bytes in thread 000c eip 4045ec30 esp 405c0ed0 stack 0x405c0000-0x405c4000 [mduarte@mduarte setup]$ Somebody can give tips to discover the problem to me? Running +relay is too slow in my machine, but I hava a 1.2MB log. I have little time that I can dedicate to the Wine, but go to try to make this today and tomorrow. Here is the part of +relay where the error occurs and system hangs: 000c:Call ntdll.RtlInitAnsiString(405c3c6c,406867c0 "Software\\Wine\\Wine\\Config\\Tweak.Fonts") ret=405e32a4 000c:Ret ntdll.RtlInitAnsiString() retval=00000000 ret=405e32a4 000c:Call ntdll.RtlAnsiStringToUnicodeString(40018bf8,405c3c6c,00000000) ret=405e32ad 000c:Ret ntdll.RtlAnsiStringToUnicodeString() retval=00000000 ret=405e32ad 000c:Call ntdll.NtOpenKey(405c3d78,000f003f,405c3c74) ret=405e32d3 000c:Ret ntdll.NtOpenKey() retval=c0000034 ret=405e32d3 000c:Call ntdll.RtlNtStatusToDosError(c0000034) ret=405e32b7 000c:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=405e32b7 000c:Ret advapi32.RegOpenKeyA() retval=00000002 ret=4066f28c 000c:Call kernel32.LoadLibrary16(40686903 "GDI.EXE") ret=4066f2a3 err:seh:setup_exception stack overflow 460 bytes in thread 000c eip 4045ec30 esp 405c0e34 stack 0x405c0000-0x405c4000 Thanks in advance. > Em Qua 05 Nov 2003 22:30, Marcelo Duarte escreveu: > > Hi all, > > > > Some days ago, I have some problems with my application developed in > > Visual Foxpro 3, that before the end of separation of kernel, runs with > > some issues, but runs. The problems resides in a call to dlls and > > library (in VFP, the comand SET LIBRARY calls a especial type of DLL) and > > the 3 forms is accepted: 1) SET LIBRARY TO FOXTOOLS > > 2) SET LIBRARY TO FOXTOOLS.FLL > > 3) SET LIBRARY TO "FOXTOOLS.FLL" > > In wine, after the end of separation fase, in the new wine-20031016, only > > the (3) is accepted, and accutually (the last CVS) the forms 1, 2 and 3, > > appear to be running, and I will investigate.... > > But, the usage of external DLLs is broken. > > Exist the comand DECLARE, wich declares a function in a dll, and as > > example, I use this: > > DECLARE INTEGER GetLogicalDriveStrings IN WIN32API; > > INTEGER nLen, STRING @sBuf > > > > and call: > > nLen = GetLogicalDriveStrings(MAX_DRIVES, @sBuf) > > > > When the calls fire, the programs terminates, a messagebox appear with > > text "Invalid indentifier" and some others erros and wine returns the > > following errors: > > > > [mduarte@mduarte MODULLUS.300]$ wine modullus > > fixme:font:WineEngAddFontResourceEx :stub > > fixme:font:WineEngAddFontResourceEx :stub > > [mduarte@mduarte MODULLUS.300]$ wine: Unhandled exception (thread 000b), > > starting debugger... > > WineDbg starting on pid a > > Loaded debug information from ELF 'wine' ((nil)) > > Breakpoint 1 at 0x4000d484 (_end+0x400a660) > > Loaded debug information from ELF '/usr/local/lib/libwine.so.1' > > (0x40028000) No debug information in ELF '/lib/libc.so.6' (0x4003f000) > > No debug information in ELF '/lib/libdl.so.2' (0x40184000) > > No debug information in ELF '/lib/libm.so.6' (0x40187000) > > Loaded debug information from ELF '/lib/ld-linux.so.2' (0x40000000) > > Loaded debug information from ELF '/usr/local/lib/wine/ntdll.dll.so' > > (0x401aa000) > > Loaded debug information from ELF '/usr/local/lib/libwine_unicode.so.1' > > (0x40216000) > > No debug information in ELF '/lib/libnss_files.so.2' (0x4001a000) > > Loaded debug information from ELF '/usr/local/lib/wine/kernel32.dll.so' > > (0x40420000) > > Loaded debug information from ELF '/usr/local/lib/wine/user32.dll.so' > > (0x40680000) > > Loaded debug information from ELF '/usr/local/lib/wine/gdi32.dll.so' > > (0x407ab000) > > Loaded debug information from ELF '/usr/local/lib/wine/advapi32.dll.so' > > (0x4081b000) > > Loaded debug information from ELF '/usr/local/lib/wine/winspool.drv.so' > > (0x40847000) > > Loaded debug information from ELF '/usr/local/lib/wine/comdlg32.dll.so' > > (0x40869000) > > Loaded debug information from ELF '/usr/local/lib/wine/shell32.dll.so' > > (0x408e1000) > > Loaded debug information from ELF '/usr/local/lib/wine/ole32.dll.so' > > (0x4095d000) > > Loaded debug information from ELF '/usr/local/lib/wine/rpcrt4.dll.so' > > (0x409cc000) > > Loaded debug information from ELF '/usr/local/lib/wine/shlwapi.dll.so' > > (0x40a11000) > > Loaded debug information from ELF '/usr/local/lib/wine/comctl32.dll.so' > > (0x40a64000) > > Loaded debug information from ELF '/usr/local/lib/wine/version.dll.so' > > (0x40af9000) > > Loaded debug information from ELF '/usr/local/lib/wine/lz32.dll.so' > > (0x40b12000) > > Loaded debug information from ELF '/usr/local/lib/wine/mpr.dll.so' > > (0x40b28000) > > Loaded debug information from ELF '/usr/local/lib/wine/winmm.dll.so' > > (0x40b41000) > > Loaded debug information from ELF '/usr/local/lib/wine/x11drv.dll.so' > > (0x40ba6000) > > No debug information in ELF '/usr/X11R6/lib/libSM.so.6' (0x40561000) > > No debug information in ELF '/usr/X11R6/lib/libICE.so.6' (0x40c21000) > > No debug information in ELF '/usr/X11R6/lib/libXrandr.so.2' (0x4030b000) > > No debug information in ELF '/usr/X11R6/lib/libXrender.so.1' (0x40571000) > > No debug information in ELF '/usr/X11R6/lib/libXext.so.6' (0x40c38000) > > No debug information in ELF '/usr/X11R6/lib/libX11.so.6' (0x40c46000) > > No debug information in ELF '/usr/lib/libGL.so.1' (0x40d0e000) > > No debug information in ELF '/usr/X11R6/lib/libXmu.so.6' (0x40ebb000) > > No debug information in ELF '/usr/X11R6/lib/libXt.so.6' (0x40ed1000) > > No debug information in ELF '/usr/X11R6/lib/libXi.so.6' (0x40f23000) > > No debug information in ELF '/lib/libpthread.so.0' (0x40f2b000) > > No debug information in ELF '/usr/X11R6/lib/libXcursor.so.1' (0x40f7c000) > > No debug information in ELF > > '/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2' (0x4056a000) > > No debug information in ELF > > '/usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2' (0x40f85000) > > Loaded debug information from ELF '/usr/local/lib/wine/wineoss.drv.so' > > (0x410c0000) > > Loaded debug information from ELF '/usr/local/lib/wine/msacm.drv.so' > > (0x410fb000) > > Loaded debug information from ELF '/usr/local/lib/wine/msacm32.dll.so' > > (0x41112000) > > Loaded debug information from ELF '/usr/local/lib/wine/midimap.drv.so' > > (0x41250000) > > Loaded debug information from ELF '/usr/local/lib/wine/ctl3d32.dll.so' > > (0x41371000) > > No debug information in 32bit DLL 'C:\windows\system\VFP300.ESL' > > (0x400000) No debug information in 32bit DLL 'NTDLL.DLL' (0x401c0000) > > No debug information in 32bit DLL 'KERNEL32.DLL' (0x40450000) > > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' > > (0x40830000) > > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' > > (0x407c0000) No debug information in 32bit DLL > > 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x406a0000) No debug information in 32bit > > DLL 'C:\WINDOWS\SYSTEM\WINSPOOL.DRV' (0x40850000) > > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' > > (0x409e0000) No debug information in 32bit DLL > > 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40980000) No debug information in 32bit > > DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x40a30000) No debug information in > > 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40a70000) > > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' > > (0x40900000) No debug information in 32bit DLL > > 'C:\WINDOWS\SYSTEM\COMDLG32.DLL' (0x40880000) > > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' > > (0x40b20000) No debug information in 32bit DLL > > 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x40b00000) No debug information in > > 32bit DLL 'C:\WINDOWS\SYSTEM\MPR.DLL' (0x40b30000) No debug information > > in 32bit DLL > > 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x40b50000) No debug information in 32bit > > DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40bc0000) No debug information in > > 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x410d0000) No debug > > information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM32.DLL' (0x41120000) No > > debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM.DRV' (0x41100000) > > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MIDIMAP.DRV' > > (0x41260000) No debug information in 32bit DLL > > 'C:\WINDOWS\SYSTEM\CTL3D32.DLL' (0x41380000) Unhandled exception: page > > fault on write access to 0x55bd0565 in 32-bit code (0x00405732). > > In 32-bit mode. > > 0x00405732 (VFP300.ESL..text+0x3732 in VFP300.ESL): movl > > %edx,0x0(%eax) Wine-dbg>WineDbg terminated on pid a > > > > The winedbg crahes.... > > > > The wine-20030911 runs fine. > > Can someone help me how to correct, or where to find the problem? -- Marcelo Duarte

1 1

configure features summary patch
by Chris Morgan 23 Nov '03

23 Nov '03

Lionel was wondering why just print out the status of openGL, why not of other optional features. I tried to get all of the important ones, comments and suggestions welcome. This patch is intended to replace the previous one. Chris

1 0

Segmentation fault with "./pgm" but not with "wine ./pgm"
by Sundial Services International Inc 23 Nov '03

23 Nov '03

After updating Linux (glibc) the following problem has surfaced: [#1] If a Win32 executable is run from the shell with "./pgmname" the program does not run but produces the message "segmentation fault." (If there is a traceback or log then I don't know how to get it.) [#2] However: if the program is run with "wine ./pgmname" the program runs normally. Perhaps the most basic problem I have here is that, in scenario #1 when all I get is "segmentation fault," I don't know how to get more info, a traceback or a log. System is RHLinux 8.0, Wine 20030318, which ran just fine in both scenarios until an update was applied which included glibc. Incidentally, I rebuilt Wine from source and even rebooted the machine (sigh, thus ending 100-odd days of uptime) with no effect on the prob. Obviously if I knew how to see the real failure-message I could probably shoot it.

2 1

Re: Fixes to wininet.dll
by Uwe Bonnes 23 Nov '03

23 Nov '03

>>>>> "Jens" == Jens Briesofsky <jeb(a)swym.net> writes: Jens> My first set of patches contributed to wine, the results of my Jens> struggle getting Climateprediction.net to work... Perhaps consider writing test cases for yoyr finding to. Look at ../wininet/test/ how that is done. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

configure patch to be clear about the state of opengl support
by Chris Morgan 23 Nov '03

23 Nov '03

Someone on irc had trouble with opengl, it wasn't clear whether opengl support was enabled or not. Thought I might throw out a patch to make things more explicit. Chris

1 0

Re: Japanese default GuiFont
by Shachar Shemesh 23 Nov '03

23 Nov '03

Hi, Are you the same guy who does maintains the ODBC driver for Postgresql? Shachar Hiroshi Inoue wrote: -- Shachar Shemesh Open Source integration & consulting Home page & resume - http://www.shemesh.biz/

1 1

WineX relation to Wine
by Gerhard W. Gruber 22 Nov '03

22 Nov '03

I was wondering what is the relation of Wine to WineX? There is a CVS access to WineX, at least part of it, which is covered under the GPL. What I was wondering about is, wether this code is the same as wine or is it more advanced? Or is this code only the sutff which is also contained in Wine and all the other stuff is (more or less) closed, so that you can not use it for Wine. I was thinking about subscribing to WineX, at least a test for this three month account, to see if the games, I'm interested in, will work. But then I wonder what this would mean if I do some work for Wine. Is this a problem? Can Wine and WineX co-exist as an installation and for development? I know that I was not exactly busy for wine right now, but I try to get pICE in a state where it will be usefull for wine development, because this is my primary goal, but if this will be a problem after being subscribed to WineX I would rather not subscribe and stick with Wine instead. -- Gerhard Gruber Maintainer of SoftICE for Linux - http://sourceforge.net/projects/pice Fast application launcher - http://sourceforge.net/projects/launchmenu

6 13

Compiling Wine: tokenize.c problem
by Paul Barclay 22 Nov '03

22 Nov '03

I hope this is the right list for this. Version 20031118 redhat 9 After running ./tools/wineinstall everything goes ok until i get the following: . . . . make[2]: Leaving directory `/home/pbarclay/downloads/wine-20031118/dlls/mshtml' make[2]: Entering directory `/home/pbarclay/downloads/wine-20031118/dlls/msi' gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o tokenize.o tokenize.c tokenize.c:46: `TK_ABORT' undeclared here (not in a function) tokenize.c:46: initializer element is not constant tokenize.c:46: (near initialization for `aKeywordTable[0].tokenType') tokenize.c:46: initializer element is not constant tokenize.c:46: (near initialization for `aKeywordTable[0]') tokenize.c:47: `TK_AFTER' undeclared here (not in a function) tokenize.c:47: initializer element is not constant tokenize.c:47: (near initialization for `aKeywordTable[1].tokenType') tokenize.c:47: initializer element is not constant tokenize.c:47: (near initialization for `aKeywordTable[1]') tokenize.c:48: `TK_ALL' undeclared here (not in a function) . . . . tokenize.c:296: `TK_ILLEGAL' undeclared (first use in this function) tokenize.c:305: `TK_BITOR' undeclared (first use in this function) tokenize.c:308: `TK_CONCAT' undeclared (first use in this function) tokenize.c:313: `TK_COMMA' undeclared (first use in this function) tokenize.c:317: `TK_BITAND' undeclared (first use in this function) tokenize.c:321: `TK_BITNOT' undeclared (first use in this function) tokenize.c:336: `TK_STRING' undeclared (first use in this function) tokenize.c:341: `TK_DOT' undeclared (first use in this function) tokenize.c:348: `TK_INTEGER' undeclared (first use in this function) tokenize.c:353: `TK_FLOAT' undeclared (first use in this function) tokenize.c:370: `TK_ID' undeclared (first use in this function) make[2]: *** [tokenize.o] Error 1 make[2]: Leaving directory `/home/pbarclay/downloads/wine-20031118/dlls/msi' make[1]: *** [msi] Error 2 make[1]: Leaving directory `/home/pbarclay/downloads/wine-20031118/dlls' make: *** [dlls] Error 2 Could somebody offer a way to fix this? Thanks PB ________________________________________________________________________ E-mail is an informal method of communication and may be subject to data corruption, interception and unauthorised amendment for which Digital Bridges Ltd will accept no liability. Therefore, it will normally be inappropriate to rely on information contained on e-mail without obtaining written confirmation. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. ________________________________________________________________________

1 0

Re: help with linking needed
by Ralf Juengling 22 Nov '03

22 Nov '03

> I have successfully compiled sources of a Windows application, but > when starting up, it tries to locate and link to a windows dll > to access some C library functions: > > ... > err:module:import_dll No implementation for cw3230.DLL._strlen imported > from L"Z:\\local\\builts\\phaeaco-20031119\\src\\memview\\memview.exe", > setting to 0xdeadbeef > err:module:import_dll No implementation for cw3230.DLL._strncpy imported > from L"Z:\\local\\builts\\phaeaco-20031119\\src\\memview\\memview.exe", > setting to 0xdeadbeef > err:module:import_dll No implementation for cw3230.DLL._strtok imported > from L"Z:\\local\\builts\\phaeaco-20031119\\src\\memview\\memview.exe", > setting to 0xdeadbeef > err:module:import_dll No implementation for cw3230.DLL._tolower imported > from L"Z:\\local\\builts\\phaeaco-20031119\\src\\memview\\memview.exe", > setting to 0xdeadbeef > err:module:import_dll No implementation for cw3230.DLL._toupper imported > from L"Z:\\local\\builts\\phaeaco-20031119\\src\\memview\\memview.exe", > setting to 0xdeadbeef > err:module:LdrInitializeThunk Main exe initialization failed, status > c0000135 > > First of all: Where does the name "cw3230.DLL" come from -- Wine didn't > install such a dll on my system? Okay, I found the answer to this myself, it is quite embarrassing: Amid the sources that I got there was also the executable compiled on a Windows system by a Borland compiler. Since the winelib-generated make file creates a shared library and not an executable, the spurious native Windows executable was not overwritten by my built. The wineapploader script then started wine with the native Windows executable instead of the shared library "memview.exe.so", and the missing DLL reported above is probably Borlands C runtime library or part of it. So forget about the other questions in my previous posting. Now the problem is that the applicaiton doesn't start but immediately fails with a Segmentation Fault. The problem seems to be in the function GetFullName in files/dos_fs.c; here are the last four lines of a startup trace: 0009:trace:nls:WideCharToMultiByte cp 65010 L"memview.exe" -> "memview.exe" 0009:trace:dosfs:DOSFS_FindUnixName (/local/builts/phaeaco-20031119/src/memview,L"memview.exe") -> L"memview.exe" (L"MEMVIEW.EXE") 0009:trace:heap:RtlFreeHeap (0x401e0000,00000002,401e0918): returning TRUE 0009:trace:dosfs:DOSFS_GetFullName returning /local/builts/phaeaco-20031119/src/memview/memview.exe = L"Z:\\LOCAL\\BUILTS\\PHAE~WVJ\\SRC\\MEMVI\ EW\\MEMVIEW.EXE" Segmentation fault (Note: I had renamed the file "memview.exe.so" to "memview.exe"). I haven't looked into and tried to fix GetFullName yet but will do so next week. Of course, I hope somebody who knows the code well will come up with a fix before I try. :-) Thanks for the Wine, Ralf

1 0

Re: help with linking needed
by Ralf Juengling 22 Nov '03

22 Nov '03

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
28
Older →

Jump to page:

2025

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 November 2003