Re: Callwave doesn't run

[Steven Walter]

On Sat, Sep 22, 2001 at 09:55:10PM +0200, eric pouech wrote:
> what's strange is that the relay posted only targets the debugger
> process, not
> the process creating the exception...
> (the one creating the exception is 080671f0 and never shows up in the
> trace)
> how did you run your program ? which wine version are you using ?
> (from your previous post, the debugger now starts)

Yes, the debugger starts, but I don't really think its configured
correctly, still.  In order to get it to start, I have to start wine
from the directory I built it, so that it will find ./debugger/winedbg.
Shouldn't it look in the path for "winedbg," rather than only the
current directory?

Anyway, I started the program, from the directory where I built wine, as
"wine -debugmsg +relay 'c:\iamsetup.exe'"  Wine version is CVS from
yesterday, though it has occurred in the CVS version for several weeks;
I've never not had the problem.

Possibly an interesting note, when I run as "wine -debugmsg +relay", and
the debugger is unable to start for whatever reason, no messages are
printed that aren't also printed with just "wine".  "wine -debugmsg
+all" does, however, log extra stuff.  Attached is the latter part of what
that yields.