Wine and glibc 3.2.x

Kevin DeKorte kdekorte at yahoo.com
Fri Mar 21 16:38:18 CST 2003


The workaround given does NOT work with the glibc 2.3 provided with the 
current Red Hat 8.0 from UP2DATE

This script and code worked prior to the RedHat glibc upgrade

--- this is winword 
FNAME=`wine -- winepath -l "$1"`
wine -- "/wine/c/Program Files/Microsoft Office/Office/WINWORD.exe" "$FNAME"

--- run dump

[kdekorte at localhost kdekorte]$ LD_ASSUME_KERNEL=2.2.5
[kdekorte at localhost kdekorte]$ export LD_ASSUME_KERNEL
[kdekorte at localhost kdekorte]$ winword
wine: Unhandled exception, starting debugger...
FIXME:pthread_cond_init
WineDbg starting on pid a
Loaded debug information from ELF 'wine' (0x00000000)
Breakpoint 1 at 0x4000bb00 (_end+0x37fb0364)
Loaded debug information from ELF '/usr/local/lib/libntdll.dll.so' 
(0x4002b000)
Loaded debug information from ELF '/usr/local/lib/libwine.so' (0x40112000)
Loaded debug information from ELF '/usr/local/lib/libwine_unicode.so.1' 
(0x40129000)
No debug information in ELF '/lib/libm.so.6' (0x4020a000)
No debug information in ELF '/lib/libc.so.6' (0x4022c000)
No debug information in ELF '/lib/libdl.so.2' (0x40369000)
No debug information in ELF '/lib/ld-linux.so.2' (0x40000000)
No debug information in ELF '/lib/libnss_files.so.2' (0x4036d000)
Loaded debug information from ELF '/usr/local/lib/wine/advapi32.dll.so' 
(0x408b3000)
Loaded debug information from ELF '/usr/local/lib/wine/kernel32.dll.so' 
(0x408de000)
Loaded debug information from ELF '/usr/local/lib/wine/gdi32.dll.so' 
(0x40981000)
Loaded debug information from ELF '/usr/local/lib/wine/ole32.dll.so' 
(0x409f5000)
Loaded debug information from ELF '/usr/local/lib/wine/user32.dll.so' 
(0x40a60000)
Loaded debug information from ELF '/usr/local/lib/wine/rpcrt4.dll.so' 
(0x40b7b000)
Loaded debug information from ELF '/usr/local/lib/wine/shell32.dll.so' 
(0x40bbf000)
Loaded debug information from ELF '/usr/local/lib/wine/shlwapi.dll.so' 
(0x40c37000)
Loaded debug information from ELF '/usr/local/lib/wine/comctl32.dll.so' 
(0x40c81000)
Loaded debug information from ELF '/usr/local/lib/wine/winspool.drv.so' 
(0x40d13000)
No debug information in ELF '/usr/lib/libfreetype.so.6' (0x40d55000)
Loaded debug information from ELF '/usr/local/lib/wine/x11drv.dll.so' 
(0x40d9b000)
No debug information in ELF '/usr/X11R6/lib/libSM.so.6' (0x40d35000)
No debug information in ELF '/usr/X11R6/lib/libICE.so.6' (0x40e01000)
No debug information in ELF '/usr/X11R6/lib/libXext.so.6' (0x40e18000)
No debug information in ELF '/usr/X11R6/lib/libX11.so.6' (0x40e26000)
No debug information in ELF '/usr/lib/libGL.so.1' (0x40f04000)
No debug information in ELF '/lib/libpthread.so.0' (0x40f77000)
No debug information in ELF '/usr/X11R6/lib/libXrender.so.1' (0x40379000)
No debug information in ELF 
'/usr/X11R6/lib/X11/locale/common/xlcUTF8Load.so.2' (0x4001a000)
No debug information in ELF '/usr/X11R6/lib/X11/locale/common/ximcp.so.2' 
(0x41020000)
No debug information in 32bit DLL 'C:\Program Files\Microsoft 
Office\Office\WINWORD.EXE' (0x30000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x40060000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' 
(0x40900000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' 
(0x408c0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x409a0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40a80000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40b90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40a10000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT 
OFFICE\OFFICE\MSO9.DLL' (0x308c0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x40c50000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' 
(0x40c90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x40be0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINSPOOL.DRV' 
(0x40d20000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40db0000)
Unhandled exception: page fault on write access to 0x403c3504 in 32-bit code 
(0x3003be4c).
In 32-bit mode.
0x3003be4c (WINWORD.EXE.EntryPoint+0x394a4 in C:\Program Files\Microsoft 
Office\Office\WINWORD.EXE): movl       %ecx,0x1486c(%eax)
Wine-dbg>quit
WineDbg terminated on pid a
[kdekorte at localhost kdekorte]$



Kevin


On Friday 21 March 2003 02:44 pm, Dan Kegel wrote:
> davide.giannotti at itsplanet.com wrote:
> > Ok, i recently compiled and upgraded to glibc 3.2.1 and there's no way to
> > make wine work. There's thread related bug.
> > New Red Hat, Suse and Mandrake will be shipped with this new version of
> > glibc, so i think that's a serious bug.
>
> We were all quite concerned about it until somebody reported a workaround;
> see http://www.winehq.com/hypermail/wine-devel/2003/02/0260.html
> The workaround is to give the command
>    export LD_ASSUME_KERNEL=2.2.5
> before running Wine (and probably before running configure, too).
> (This is documented in each distro's beta release notes, e.g.
> http://distro.ibiblio.org/pub/Linux/distributions/redhat/beta/phoebe/en/os/
>i386/RELEASE-NOTES.html ) Have you tried this yet?
> What CPU and OS are you using?
>
> > Configure cannot even check that libc are reentrant, i'm not a glibc
> > expert but there's some error with _errno and _errno_location.
> > I tried to apply a patch i found in the patch mailing list, but it didn't
> > work either.
> > ( http://www.winehq.com/hypermail/wine-patches/2003/01/0338.html )
>
> That patch was bogus, it is not the right fix.  The right fix is
> for Wine to adapt to the new threading model in glibc2.3 (not 3.2, I
> think), which is far superior to the old one.  See
> http://www.kegel.com/c10k.html#threads.nptl
>
> > So, consider that every linux distribution will be shipped with the new
> > glibc, and that there will be really a few windows programs that can work
> > without thread support.... well... i'd think about give priority to solve
> > this one.
>
> The changes needed are deep.  Alexandre has started on them, but
> given the workaround, it can probably wait a bit.
>
> See also
> http://www.winehq.com/hypermail/wine-devel/2003/02/0252.html
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83254
> http://redhat.ifsic.univ-rennes1.fr/_rawhide/glibc-devel-2.3.1-51.i386.html



More information about the wine-devel mailing list