Hi,
Using some programs with wine (last CVS), the debugger enters a loop and cannot be stopped other way than a kill on it.
If I let it go, i see pages of these : Wine-dbg>parse error Cannot pass on last chance exception. You must use cont Wine-dbg>parse error Cannot pass on last chance exception. You must use cont Wine-dbg>parse error Cannot pass on last chance exception. You must use cont
Had someone the same behaviour ? RH 7.2, kernel 2.4.9-31, glibc-2.2.4-24
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle a écrit :
Hi,
Using some programs with wine (last CVS), the debugger enters a loop and cannot be stopped other way than a kill on it.
If I let it go, i see pages of these : Wine-dbg>parse error
some questions: - do you use the wineconsole or directly from the Unix console - was winedbg started from an exception or from the command line - did you try to redirect input and/or output to some files
(sounds like an error in reading the input stream, which doesn't seem to be correctly set up)
A+
some questions:
- do you use the wineconsole or directly from the
Unix console
I run it directly from the Unix console.
- was winedbg started from an exception or from the
command line
from an exception
- did you try to redirect input and/or output to
some files
no, was the direct output on the Unix console. Redirect as >stdout_log 2>stderr_log gives the same messages in the file stderr_log.
(sounds like an error in reading the input stream, which doesn't seem to be correctly set up)
A+
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle a écrit :
some questions:
- do you use the wineconsole or directly from the
Unix console
I run it directly from the Unix console.
could you try to run it from the wineconsole (use set $UseXTerm = 1 in a winedbg session and exit winedbg to use that as a default setting)
could you send me the -debugmsg +console,+server (at least the part when the debugger is started and fails on line reading)
TIA