Wine-dbg> wine_dbg_cmd: Exception c000013a fatal flex scanner internal error--end of buffer missed
In the above example I pressed CTRL-C on the commandline from Winedbg. The exception message is shown and a dbg xterm window has been opened. After exiting from gdb winedbg exits.
Is this a bug? I suppose so. :)
Gerhard W. Gruber wrote:
Wine-dbg> wine_dbg_cmd: Exception c000013a fatal flex scanner internal error--end of buffer missed
In the above example I pressed CTRL-C on the commandline from Winedbg. The exception message is shown and a dbg xterm window has been opened. After exiting from gdb winedbg exits.
Is this a bug? I suppose so. :)
no... it's the expected behaviour when you run winedbg outside of wineconsole (there's no support for Ctrl-C handling)
run it instead with wineconsole winedbg
A+
no... it's the expected behaviour when you run winedbg outside of wineconsole (there's no support for Ctrl-C handling)
run it instead with wineconsole winedbg
Is it not possible to link it against readline, or does winedbg have to be LGPLd also?
Eric Pouech wrote:
Gerhard W. Gruber wrote:
Wine-dbg> wine_dbg_cmd: Exception c000013a fatal flex scanner internal error--end of buffer missed
In the above example I pressed CTRL-C on the commandline from Winedbg. ... Is this a bug? I suppose so. :)
no... it's the expected behaviour when you run winedbg outside of wineconsole (there's no support for Ctrl-C handling)
run it instead with wineconsole winedbg
Tell me you're joking. I hate wineconsole; why should I have to use it when I want to use winedbg? - Dan
Tell me you're joking. I hate wineconsole; why should I have to use it when I want to use winedbg?
if you want to have proper Ctrl-C handling, you have to use wineconsole
IOW, winedbg is a winelib app and gets its input from win32 console
feel free to write another input driver (from bare unix streams) which would put the unix-console in raw mode to handle properly the ctrl-c
A+
Eric Pouech wrote:
Tell me you're joking. I hate wineconsole; why should I have to use it when I want to use winedbg?
if you want to have proper Ctrl-C handling, you have to use wineconsole
IOW, winedbg is a winelib app and gets its input from win32 console
feel free to write another input driver (from bare unix streams) which would put the unix-console in raw mode to handle properly the ctrl-c
That'd be the wrong approach. You don't want to handle "control c", you want to handle SIGINT. - Dan
That'd be the wrong approach. You don't want to handle "control c", you want to handle SIGINT.
mixing Win32 signals and Unix signals is not a very good idea either in Winelib programs... but approach sounds ok, I've made a patch against Win32 exception handlers for this
A+
Eric Pouech wrote:
That'd be the wrong approach. You don't want to handle "control c", you want to handle SIGINT.
mixing Win32 signals and Unix signals is not a very good idea either in Winelib programs... but approach sounds ok, I've made a patch against Win32 exception handlers for this
Man, I just can't stay angry very long around here. Thanks! - Dan
Man, I just can't stay angry very long around here. Thanks!
if you could not be angry for a couple of days, that'd be nice too ;-)))) A+
-
Dan Kegel -
Eric Pouech -
Gerhard W. Gruber -
Mike Hearn