[Openmcl-devel] Issues with ccl:process-interrupt

David Findlay dave.findlay at roke.co.uk
Mon Jul 6 13:39:22 UTC 2009


Hi,

I've been successfully using CCL on Mac OS (both 32-bit PPC and 64-bit x86
platforms) and Linux (64-bit x86) for some while.

With the additional support for 32-bit x86 platforms provided by CCL 1.3, I
have tried running my application on some 32-bit platforms, but without
success. The problem seems related to ccl:process-interrupt. There seem to
be two different issues: one on 32-bit x86 Linux platforms, and one on
Windows platforms. In both cases, the issue can be demonstrated by typing
the following form at the listener:

(ccl:process-run-function "foo"
  (lambda (p) (ccl:process-interrupt p #'print 'hi))
  ccl:*current-process*)

(That is, make a process to interrupt the listener and cause it to print
HI.)

1. On the Linux platform, the return value from process-run-function is
printed, and then Lisp simply exits with a Trace/BPT trap.

2. On the Windows platform, the return value from process-run-function is
printed, and then ... nothing. Just the Lisp reader prompt. Only when the
*next* form is entered does Lisp condescend to execute the interrupting
#'print and output the HI.

I haven't been able to find any reference to these behaviours on the
clozure.com website. Are these known issues?

Thanks

David Findlay


-- 
Roke Manor Research Ltd, Romsey,
Hampshire, SO51 0ZN, United Kingdom

A Siemens company
Registered in England & Wales at:
Siemens plc, Faraday House, Sir William Siemens Square,
Frimley, Camberley, GU16 8QD. Registered No: 267550
------------------------------------------------------------------------
Visit our website at www.roke.co.uk
------------------------------------------------------------------------
The information contained in this e-mail and any attachments is
proprietary to Roke Manor Research Ltd and must not be passed to any
third party without permission. This communication is for information
only and shall not create or change any contractual relationship.
------------------------------------------------------------------------

Please consider the environment before printing this email




More information about the Openmcl-devel mailing list