Tried a different tack ....
alaric at babcom.com
Thu Oct 4 17:38:39 CDT 2001
On Thu, Oct 04, 2001 at 11:28:25PM +0000, gerard patel wrote:
> 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
> ~/.wine/system.reg :
> [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.
Gladly, if I could find winedbg anywhere.
Is there any significance to the 988300179, and if so, what is it?
********* Fight Back! It may not be just YOUR life at risk. *********
phil stracchino :: alaric at babcom.com :: halmayne at sourceforge.net
unix ronin :::: renaissance man :::: mystic zen biker geek
2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold)
Linux Now! ...because friends don't let friends use Microsoft.
More information about the wine-users