Re: interrupt signal in MSW

> 
>> GenerateConsoleCtrlEvent(CTRL_BREAK_EVENT, pid)
>> acts as Ctrl+Break were pressed, instead. This event immediately crashes clisp on Windows, currently.
>> But that might not be a bug but a convenient way to enter an eventually-running debugger => In case that
>> Ctrl+C doesn't work on Windows: Is there a way to make use of this event, instead?
> 
> "crashes" or terminates? See
> https://gitlab.com/gnu-clisp/clisp/blob/master/src/win32aux.d#L46
> /* Ctrl-C-interruptibility.
>  We treat Ctrl-C as under Unix: Enter a break loop, continuable if possible.
>  We treat Ctrl-Break as usual under Windows: abort the application, as if
>  (exit t) was called, with exit code 130.
> 

I will have a look at it tomorrow.

> I don't believe Ctrl-Break is configurable. See line 147 of this file:
>     } else {
>       if (interruptible_abort_code == 1+CTRL_BREAK_EVENT) {
>         final_exitcode = 130; quit(); /* aborted by Ctrl-Break */
> 
> However Ctrl-C ought to work. Does it work when you invoke clisp directly in a console, without GUI, on your machine?
> E.g. can you interrupt a REPL running (CL:LOOP)?
> 
> 

The lisp was invoked via a batch file that was invoked from the console
(cmd.exe). With sbcl that worked fine. But perhaps that is the problem.

Will make new tests tomorrow.

Kind regards,

     Gunter.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list