You could perhaps send it to the list to have some feedback before
posting it to wine-patches...
> You will likely find that the current winejack driver is not that
> reliable. I have fixed a few major bugs in the winejack waveout code,
> and am about 95% done implementing wave in. I am going on v
Chris Morgan wrote:
I did export WINELOADER=`which wine` and it set it to
/usr/local/bin/wine I'll check my machine to ensure that I don't have
multiple copies of the wine or winedbg binaries.
Note that I am getting debug information from wine dlls now, I do not if
I don't set the WINELOADER e
I did export WINELOADER=`which wine` and it set it to
/usr/local/bin/wine I'll check my machine to ensure that
I don't have multiple copies of the wine or winedbg
binaries.
Note that I am getting debug information from wine dlls
now, I do not if I don't set the WINELOADER environment
variabl
Chris Morgan wrote:
Should winedbg be able to load symbols up for non-wine libraries? After the
export WINELOADER idea I've got wine symbols but I'm still trying to debug a
bizzare crash in winejack where I get:
it should
it seems more to me that the wine exec that winedbg is looking at is not
Hello,
I don't have any answer to your question, but I do know "why" wine is crashing. It is
indeed crashing inside of jack_activate() in libjack. If you look in that function,
the first thing to does is allocate a 1MB array (which it never uses). I am not really
sure why they do this -- there
Should winedbg be able to load symbols up for non-wine libraries? After the
export WINELOADER idea I've got wine symbols but I'm still trying to debug a
bizzare crash in winejack where I get:
~/c$ wine sndrec32.exe
Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
Segmentat
