On Fri, 6 Aug 2004 09:26:59 +0200 (CEST), you wrote: > Hello Rein, > > thank you for your hint with the pass statement. > Now I went two steps further: > > (continued) > 0x100d8f4a: movb 0x9a(%ecx),%dl > Wine-dbg>pass > Unhandled exception: page fault on read access to 0x0000009a in 32-bit > code (0x100d8f4a). > Register dump: > CS:0023 SS:002b DS:002b ES:002b FS:003b GS:0033 > EIP:100d8f4a ESP:003ef7bc EBP:003ef7d0 EFLAGS:00010246( - 00 -RIZP1) > EAX:00000000 EBX:0086fac8 ECX:00000000 EDX:00000000 > ESI:77df1b9e EDI:0056d7d0 > Stack dump: > 0x00000000: 00000000 00000000 00000000 00000000 > 0x00000010: 00000000 00000000 00000000 00000000 > 0x00000020: 00000000 00000000 00000000 00000000 > 0x00000030: 00000000 00000000 00000000 00000000 > 0x00000040: 00000000 00000000 00000000 00000000 > 0x00000050: 00000000 00000000 00000000 00000000 > 0x00000060: > > Backtrace: > =>1 0x100d8f4a (0x003ef7d0) > 2 0x100d8ff5 (0x003ef7dc) > 3 0x0049ed6b (0x003ef9f4) > 4 0x00491aa2 (0x003efc98) > 5 0x00416df3 (0x003efd70) > 6 0x0040319b (0x003efe94) > 7 0x0056d922 (0x003eff20) > 8 0x007d64b2 (0x003efff4) > 9 0x0064e081 (0x00000000) > 0x100d8f4a: movb 0x9a(%ecx),%dl > Wine-dbg>pass > Process of pid=0x0000000a has terminated > Wine-dbg> > > -------------------------------------------------- > The Genotyper window closes now. > > If I call "wine Genotyper.exe" the execution will stop with > > wine: Unhandled exception (thread 0009), starting debugger... > Usage: winedbg [--auto] [--gdb] cmdline > > The only posibility to continue is to press <ctrl-c> to stop the execution. > Have I got a wrong wine configuration? Probably the debugger configuration is not correct. Here is the doc: http://www.winehq.org/site/docs/wine-devel/dbg-config > Or should I upgrade to a newer wine > version than 20040615 ? Upgrading to the latest version is always a good idea. But it looks that the debugger back trace is not giving useful information about the cause of the crash. What you may try is to produce a relay log with: WINEDEBUG=+relay,+seh wine Genotyper.exe &>wine.log The resulting wine.log can be REAL BIG. Open it in an editor and search for the string "starting debugger". From that point look upwards in the log to suspicious failures. If you need help and want to show portions of the log consider entering a bug report at http://bugs.winehq.org. It has an upload facility. Rein. -- Rein Klazes rklazes@xxxxxxxxx _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
