I've just had this problem:
A program had crashed and wing-dbg has been initiated, when I pressed CTRL+C it went back to the console. however then like mad "wine-dbg>" kept appearing over and over until I exited the console.
Like "winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg>"
Over and over and over (and over... and over...... and over..... etc)
Any ideas why this is?
Oh, and on an unrelated note, I noticed that Opera 5 runs well in wine - do the newer versions run just as well?
winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg>"
Over and over and over (and over... and over...... and over..... etc)
Any ideas why this is?
The terminal modes were not reset.
David
Kye Lewis wrote:
I've just had this problem:
A program had crashed and wing-dbg has been initiated, when I pressed CTRL+C it went back to the console. however then like mad "wine-dbg>" kept appearing over and over until I exited the console.
Like "winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg> winedbg>"
Over and over and over (and over... and over...... and over..... etc)
Any ideas why this is?
this sometimes happens when the underlying terminal dies (either unix or wineconsole) either a bug in winedbg or in the wineserver it's been a while I didn't see this though
A+
-
David Laight -
Eric Pouech -
Kye Lewis