Problems using WineDbg - wine-devel

8 Dec 2004


      Ok, I'm trying to use winedbg to check, why a game doesn't work, but:
$ /cd_autorun Zeus
Using /cdimages/mnt/Zeus/AUTORUN.INF as Autorun.Inf
Using Z:\autorun.exe as Autorun.Exe
Setting WINEPREFIX to /.wine-Zeus
Starting Z:\autorun.exe using cmdline /bin/wine Z:\autorun.exe
Xlib:  extension "GLX" missing on display "localhost:0.0".
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40359328)->(0002002e,00000013)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40359328)->(0002002e,00000008)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40359328)->(0002002e,00000013)
fixme:ddraw:DIB_DirectDrawSurface_Blt dwFlags DDBLT_WAIT and/or DDBLT_ASYNC: can't handle right now.
wine: Unhandled exception (thread 000f), starting debugger...
WineDbg starting on pid 0xe
Unhandled exception: page fault on read access to 0x5a202d28 in 32-bit code (0x21113913).
In 32 bit mode.
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:1007 GS:007f
 EIP:21113913 ESP:4067f8b8 EBP:4067fcdc EFLAGS:00010206(   - 00      - RIP1)
 EAX:00000000 EBX:41a54f80 ECX:5a202d28 EDX:00737565
 ESI:403ae428 EDI:41a552e8
Stack dump:
0x4067f8b8:  41a55228 21103fa6 403ae428 41a55228
0x4067f8c8:  10029005 403ae428 0000ac44 00000000
0x4067f8d8:  100086c8 41a55228 0000ac44 00000010
0x4067f8e8:  00000002 08000000 41a54f80 4067fe0c
0x4067f8f8:  00000000 4051d10c 00000280 000001e0
0x4067f908:  00000e85 00000000 00000000 0000001e
0200: sel=1007 base=40016000 limit=00001f97 32-bit rw-
Backtrace:
=>1 0x21113913 in mss32 (+0x13913) (0x4067fcdc)
  2 0x0042300b in zeus (+0x2300b) (0x4067fdbc)
  3 0x00603f1f in zeus (+0x203f1f) (0x4067fe94)
  4 0x0060f8ae EntryPoint+0xce in zeus (0x4067ff20)
  5 0x40481a65 start_process+0x135(arg=0x0) [/wine/dlls/kernel/process.c:1046] in kernel32 (0x4067fff4)
  6 0x4001d361 wine_pthread_abort_thread+0x31(status=0x0) [port.c:85] in libwine.so.1 (0x00000000)
0x21113913: cmpl        $1,0x0(%ecx)
Wine-dbg>info registers{PRESSED ENTER}
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:1007 GS:007f
 EIP:21113913 ESP:4067f8b8 EBP:4067fcdc EFLAGS:00010206(   - 00      - RIP1)
 EAX:00000000 EBX:41a54f80 ECX:5a202d28 EDX:00737565
 ESI:403ae428 EDI:41a552e8
Wine-dbg>bt{PRESSED ENTER}
Backtrace:
=>1 0x21113913 in mss32 (+0x13913) (0x4067fcdc)
  2 0x0042300b in zeus (+0x2300b) (0x4067fdbc)
  3 0x00603f1f in zeus (+0x203f1f) (0x4067fe94)
  4 0x0060f8ae EntryPoint+0xce in zeus (0x4067ff20)
  5 0x40481a65 start_process+0x135(arg=0x0) [/wine/dlls/kernel/process.c:1046] in kernel32 (0x4067fff4)
  6 0x4001d361 wine_pthread_abort_thread+0x31(status=0x0) [port.c:85] in libwine.so.1 (0x00000000)
Wine-dbg>${PRESSED ENTER}
)Syntax Error (
Wine-dbg>WineDbg terminated on pid 0xe
{PRESSED ENTER}
$
So, in the very first seconds, I still can interact with winedbg, but then 
it suddenly disappears, and I get back my shell. No chance to investigate 
the problem using winedbg this way.
There are some other strage missbehaviors, like printing 10000 times 
'Wine-dbg>' before being killed using kill -kill <wine-pids>, or even not 
printing the register dump + back trace in the first place like shown 
above (same application, startup phase). So not even every time I try 
winedbg, everything happens identical.
I'm using wine-cvs just checked out and rebuild using command line:
$ cvs up && ./configure -C --prefix=/ && make depend && make && make install
Regards, Bodo