On Mon, 03 Dec 2001 12:49:00 +0000, "T REX" <the1trex@hotmail.com> wrote: >Here are som logg files that might help fixing the problem. > >wine log usin +comm,+file,+relay >http://www.termografinett.no/wine.log.bz2 > >strace output >http://www.termografinett.no/strace.log.bz2 > >winedbg output >http://www.termografinett.no/debugg.bz2 I have looked at wine and debugg - is there a difference between the 2 runs in the command line you use ? Are they really on the same computer ? If yes, it's deceiving because from wine.log, it looks as if just enabling debugger would give the exact source line of the crash : 0806c808:Call kernel32.ReadFile(00000060,43050000,00000400,40606988,4304a6cc) ret=0043ecff trace:file:ReadFile 96 0x43050000 1024 0x40606988 0x4304a6cc FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock trace:file:FILE_SetDosError errno = 11 Resource temporarily unavailable 0806c808:Ret kernel32.ReadFile() retval=00000000 ret=0043ecff 0806c808:Call kernel32.GetOverlappedResult(00000060,4304a6cc,40606988,00000001) ret=0043ed17 trace:file:GetOverlappedResult (96 0x4304a6cc 0x40606988 1) trace:file:GetOverlappedResult waiting on 0x4304a6cc 0806c808:Call kernel32.UnhandledExceptionFilter(404f4918) ret=00577264 Normally, it's easy to fix a crash that happens inside a Wine function. However, the debugger crash is extremely strange and I have never seen something like that. I'd suggest to scrap your current install and download current Cvs instead - I suspect that something strange may exist in your current installation. Gerard
