[Vm-dev] Oddd image lock-up on Unix
tim at rowledge.org
Mon Apr 2 21:06:16 UTC 2007
On 2-Apr-07, at 1:28 PM, Andreas Raab wrote:
> It is the very first time we've seen this kind of problem - usually
> the symptoms are 100% CPU not 0% CPU consumption ;-) This is also
> why I suspected that the delay fix might have to do with it.
What does nanosleep do with -ve params? Might it have bad behaviour
under such circumstances?
The long delay changes were tested on special VMs that pretended
quite short periods were the maximum delay length and appeared to
have no problems but it is certainly possible some problem crept into
the conversion to use full-length delays. For example the length of a
guardianDelay (see Delay>beGuardianDelay) is SmallInteger maxVal and
maybe there is some clash with the 'MillisecondClockMask' value used
interp.c? It is, after all, half of maxVal and used a lot in tick
related code. We must also note that the guardian delay stuff is only
ever used if a Delay with a non-SmallInterger length is activated,
so it is unlikely to have any effect in normal usage.
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: PUS: PUrge System
More information about the Vm-dev