[squeak-dev] Re: Latest Changes in InputSensor/EventSensor "lock up" image after save/restart?

David T. Lewis lewis at mail.msen.com
Thu Feb 4 13:38:58 UTC 2016

Hi Marcel,

Thanks /very/ much for finding the fix for this. I'm not sure how I screwed
up that startup code migration, my apologies for the errors.

I just applied your two change sets on Linux and it is good there, so I am
sure that it will be good on OS X also. That covers all the main platforms.

I would be grateful if you can commit the Kernel update to trunk. Otherwise
I will do it about 12 hours from now (I'm tied up with some other issues until
then and I don't want to risk breaking anything else in trunk until then).

Regarding the Windows difference, my guess is that the primitive fallback
code is refering to some old primitives that may have been removed from the
Windows VM but are still present in the Unix and Mac VMs. The references
to old primitives are now in method categories 'primitive-fallback', and
possibly 'primitives-cursor'.

Thank you!


On Thu, Feb 04, 2016 at 03:48:24AM -0800, marcel.taeumel wrote:
> Hi David,
> there was another issue. The EventSensor >> #shutDown code was never called.
> fix-event-sensor.2.cs
> <http://forum.world.st/file/n4875739/fix-event-sensor.cs>  
> Nevertheless, the main issue was not initializing the input semaphore in
> EventSensor >> #startUp. Which raises the question why Mac VMs can sill use
> the "old way" of fetching events? Windows VMs cannot.
> Best,
> Marcel
> --
> View this message in context: http://forum.world.st/Latest-Changes-in-InputSensor-EventSensor-lock-up-image-after-save-restart-tp4875654p4875739.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.

More information about the Squeak-dev mailing list