[Gbbopen-list] Changes to portable threads

[Dan Corkill]

> I am now back to code that was working about a month ago before
> the changes to the thread module. I am now encountering a problem
> where Lispworks signals an error:
> 
> Error: PROCESS-WAIT called when scheduling not allowed
> 
> On the stack is gbbopen::do-evfns :after
> with EVENT #<PEP::TX-TIMEOUT-EVENT>
> 
> which is one of my own event classes and a subclass of 
> gbbopen:timer-interrupt-event. This event is signalled from a Lispworks
> timer by (mp:make-timer 'signal-event 'tx-timeout-event)

The important question is who is calling PROCESS-WAIT?  GBBopen doesn't
use it any longer so I suspect it is in your code (or possibly, but less
likely, in LW itself).  A more complete backtrace would help in tracking
things down.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.