[slime-devel] Re: how to interrupt & kill function execution

[Frode Vatvedt Fjeld]

Helmut Eller <e9626484 at stud3.tuwien.ac.at> writes:

> I have only a very oldish Windows 98 and the Lisp-in-a-box package
> didn't work here.  I can only use CLISP's "base" version.  The base
> version has no win32 package and so the pid is always nil.  The
> "full" version complains about a missing function in kernel32.dll
> when GetCurrentProcessId is called.  Does
> win32::|GetCurrentProcessId| work on WinXP?  The Cygwin version uses
> system::program-id.

Right, now I changed to the "full" clisp version, and I get a PID
also. GetCurrentProcessId works fine. Unfortunately, signal-process
(the elisp function) has no effect on clisp. That is, clisp dies
immediately upon receiving signals 1 or 9, but completely ignores any
other signal.

Would it be possible, as a qick-and-dirty-hack, to poll some interrupt
flag in the (swank?) IO stream glue such that clisp can be breaked at
least if it emits some output? (Or perhaps even a once-a-second or so
timer polling could be implemented?)

Has anyone tried to talk to the clisp people about having a break
signal for a proper solution under win32?

-- 
Frode Vatvedt Fjeld