Using wine compiled from CVS yesterday.
Awdbedit is available here: http://awdbedit.sourceforge.net/
$ wine awdbedit.exe
err:rebar:REBAR_AdjustBands Phase 1 failed, x=32760, maxx=632, start=0,
end=0
err:rebar:REBAR_AdjustBands Phase 1 failed, x=32760, maxx=632, start=0,
end=0
wine: Unhandled exce
Hi Cal,
If you change the AeDebugger setting to include the --auto option:
HKLM,Software\Microsoft\WindowsNT\CurrentVersion\AeDebug,"Debugger",,"winedbg
--auto %ld %ld"
This is the default if you delete the key completely and is now also
the default if you have no registry and wine creating a
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
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" <[EMAIL PROTECTED]>> A : wine-devel@w
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 eno
or 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
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
Backtr
"Cristóvão B. B. Dalla Costa" <[EMAIL PROTECTED]> wrote:
> However, in the company I work for we will replace a hundred or so PCs
> which run Windows with Linux PCs. The people using these PCs are the
> most clueless possible, and we want to avoid aggravation from them
&g
which run Windows with Linux PCs. The people using these PCs are the
most clueless possible, and we want to avoid aggravation from them
when/if the Wine debugger shows up when an application fails. That's
inacceptable since those people would be lost and not know what to do.
However, I can
