Tried a different tack ....
lee at strictlybritishmonarchy.com
Thu Oct 4 18:00:23 CDT 2001
On Thu, 04 Oct 2001 23:38:39 +0100, Phil Stracchino awoke the pert and
nimble spirit of Usenet and gushed forth in a thuslike fashion:
> 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.
Did you say you were using a Codeweavers release?
rpm -ql codeweavers-wine, reveals it to be located at:
Remove the monarchy to email
More information about the wine-users