Re: Wine Debugger

[Pouech Eric DMI AEI CAEN]

use regedit at the beginning of your script to set the AeDebug key to a "" string (and you should have saved the key value before), and restore it at the end of your script
> Message du 31/03/05 08:47
> De : "Cal Pierog" 
> A : [e-mail]
> Copie à : 
> Objet : Wine Debugger
>
> I am trying to write a script which, at one point, needs to run the wine 
> test suite, accomplished with:
>
> make -k test
>
> Even though this skips over bad tests, it does not prevent the debugger 
> from kicking in every once in a while and asking for user input. I would 
> like this script to be robust enough to run the test suite without user 
> input, even when one of the tests fails badly enough to call the debugger.
>
> So, is there any way to disable the debugger so that the script can just 
> continue on errors and not sit at a "Wine-dbg>" prompt?
>
> Thanks,
> Cal Pierog

Wine Debugger

[Francois Gouget]

On Thu, 31 Mar 2005, Pouech Eric DMI AEI CAEN wrote:
> use regedit at the beginning of your script to set the AeDebug key to 
> a "" string (and you should have saved the key value before), and 
> restore it at the end of your script

Alternately you could add the '--auto' option and winedbg should then 
run in non-interactive mode. This will also cause it to dump a stack 
trace which is nice for later debugging if you save the output 
somewhere.

[Software\Microsoft\Windows NT\CurrentVersion\AeDebug]
"Auto"="1"
"Debugger"="winedbg.exe --auto %ld %ld"