Re: Ctl-Break Crashes
Robert wrote:>There's a known problem (see TROUBLE.DOC)
>with hitting control-C or control-Break
>when you run your program from ed. I assume the same
>problem holds for ee (you might want to ask David Cuny
>who wrote ee). The solution is to exit the editor and run
>your program normally, from the command-line, whenever you
>might want to use control-C or control-Break.
It's an effective way to toast your machine, all right. I got the vertical
pinstripe pattern on my screen (indicitive of a runaway loop filling memory
with the same value), quickly followed by a Windows error, and my machine
locking up.
EE uses a non-standard method of reading the keyboard. It looks in the
circular keyboard buffer before attempting to read from it. If the next
character is a Ctrl-C, it zaps the buffer, and returns with a Ctrl-C -
without actually *reading* the buffer. Otherwise, it tries to read the
buffer normally.
The result of this is that Ctrl-C is never processed by Euphoria, so none of
the traps can happen.
If someone were able to supply me with the scancode and/or keycode of
Ctrl-Break, I could easily add the same sort of logic for the Ctrl-Break,
and try to prevent these kinds of crashes.
I'll see if I can determine the value of Ctrl-Break myself. If I can, I'll
send Robert a fix.
However, if Ctrl-Break causes some sort of hardware interrupt to do it's
dirty work, I don't know that it would make any difference.
Thanks!
-- David Cuny
|
Not Categorized, Please Help
|
|
