The fix has been running now for roughly 24 hours with PIDs both below and above 16bit with roughly 2-30 requests per second depending on the hour, works flawlessly.
One reset from 98304 to 300 has already happened without issues. Using pil64. On Thu, Aug 7, 2014 at 2:19 PM, Alexander Burger <a...@software-lab.de> wrote: > Hi all, > > On Thu, Aug 07, 2014 at 09:00:21AM +0200, Alexander Burger wrote: >> Fixed pil32 too. I hope I didn't break anything. Tests are welcome! > > For the records: > > The handling of PIDs in both the 32-bit and the 64-bit versions of > PicoLisp itself was never a problem. They are handled in full 'pid_t' > size. > > The problem was the internal IPC protocol used by the 'tell' function, > when an (optional) PID is passed for the addressee of the message. Here, > a field of only 16 bits was used to store the PID. This is fixed now in > pil32 and pil64. > > ♪♫ Alex > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
