[Openmcl-devel] Question about 'process-interrupt run on exhausted process'
dbueno at gmail.com
Sat Feb 10 22:39:20 EST 2007
On 2/10/07, Gary Byers <gb at clozure.com> wrote:
[snip detailed and useful explanation]
> This all had something of a familiar ring to it; according to a terse
> comment in the bleeding-edge CVS logs, I did make that change shortly
> after 1.0 was released, but never backported it to 1.0.
> For 1.0, I -think- that it'd be safe to simply remove the check
> in PROCESS-INTERRUPT (in ccl/level-1/l1-processes.lisp); in this context,
> the check leads to an error that amounts to "I can't kill this dead process!":
Does this mean that one can expect the next release (FSVO "next") to
have this problem fixed?
This issue pretty much means if I release I would have to compile my
own OpenMCL and bundle it with whatever I release, should I choose to
use OpenMCL, right?
Thanks for the explanation.
More information about the Openmcl-devel