Hi all,
for some reason, the wine debugger just doesn't seem to work for me.
wine: Unhandled exception (thread 000f), starting debugger... fixme:console:SetConsoleCtrlHandler (0x405ae990,1) - no error checking or testing yet WineDbg starting on pid 0xe In 32 bit mode. Wine-dbg>bt Backtrace: =>1 0x40107b08 __read+0x28 in libc.so.6 (0x40032c54) 2 0x401cc022 Exception c0000005
The backtrace it shows appears to be from the debugger itself, not from the program? Or am I wrong in assuming this? I am getting this same backtrace for each and every program... Also, the ctrl-c key doesn't work as advertised (just does nothing).
Wine is wine cvs from 07/31, gdb is 6.1-3 from debian unstable.
Anyone got some pointers?
kr,
Chipzz AKA Jan Van Buggenhout
Unfortunately since to the move to the dbghelp DLL winedbg has been rather unstable. One thing you can do is attach to the debugger with regular gdb, and when it crashes see if you can figure out what's going wrong.
On Sun, 01 Aug 2004 17:10:42 +0200, Chipzz wrote:
Hi all,
for some reason, the wine debugger just doesn't seem to work for me.
wine: Unhandled exception (thread 000f), starting debugger... fixme:console:SetConsoleCtrlHandler (0x405ae990,1) - no error checking or testing yet WineDbg starting on pid 0xe In 32 bit mode. Wine-dbg>bt Backtrace: =>1 0x40107b08 __read+0x28 in libc.so.6 (0x40032c54) 2 0x401cc022 Exception c0000005
The backtrace it shows appears to be from the debugger itself, not from the program? Or am I wrong in assuming this? I am getting this same backtrace for each and every program... Also, the ctrl-c key doesn't work as advertised (just does nothing).
Wine is wine cvs from 07/31, gdb is 6.1-3 from debian unstable.
Anyone got some pointers?
kr,
Chipzz AKA Jan Van Buggenhout
-
Chipzz -
Mike Hearn