Tried a different tack ....
g.patel at wanadoo.fr.invalid
Thu Oct 4 18:28:25 CDT 2001
On Thu, 4 Oct 2001 13:49:56 -0700, Phil Stracchino <alaric at babcom.com>
>Is there some way I can tell wine, "Look, DON'T START any damn debugger,
>just tell me what failed"?
Starting the debugger is the best way to say why Wine failed,
because it gives a backtrace of the calls before the crash.
Now, I don't know how to setup the debugger with Codeweavers
binary release. I know only the standard source release; with
the source release all that is necessary is to add entries to
[Software\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug] 988300179
"Debugger"="/mnt/reiser/wine/debugger/winedbg %ld %ld"
Replace the path with your path to winedbg, of course.
More information about the wine-users