-- Forwarded message --
From: David T. Lewis le...@mail.msen.com
Date: Tue, Dec 7, 2010 at 2:06 AM
Subject: Re: [Vm-dev] Image freeze because handleTimerEvent and Seaside
process gone?!
To: Squeak Virtual Machine Development Discussion
vm-...@lists.squeakfoundation.org,
The changes between 1.1 and 1.1.1 are the issues in [1]. None seems related...
did I miss something?
One change that I don't understand, although it probably is unrelated, is in
[2]:
LargePositiveInteger removeSelector: #=!
LargePositiveInteger removeSelector: #bitAnd:!
LargePositiveInteger
One change that I don't understand, although it probably is unrelated, is in
[2]:
LargePositiveInteger removeSelector: #=!
LargePositiveInteger removeSelector: #bitAnd:!
LargePositiveInteger removeSelector: #bitOr:!
LargePositiveInteger removeSelector: #bitShift:!
LargePositiveInteger
On Dec 7, 2010, at 12:41 PM, Lukas Renggli wrote:
One change that I don't understand, although it probably is unrelated, is in
[2]:
LargePositiveInteger removeSelector: #=!
LargePositiveInteger removeSelector: #bitAnd:!
LargePositiveInteger removeSelector: #bitOr:!
LargePositiveInteger
The symptoms that I see are intermittent, and it's hard for me to
say what the root cause might be. It might be worthwhile to see
if you can reproduce my results. If so, it might get you closer to
a reproducible test case.
What I did was take a Pharo core 1.1, 1.1.1, and 1.2 image, and
in each
On Tue, Dec 7, 2010 at 3:41 AM, Lukas Renggli reng...@gmail.com wrote:
One change that I don't understand, although it probably is unrelated, is
in [2]:
LargePositiveInteger removeSelector: #=!
LargePositiveInteger removeSelector: #bitAnd:!
LargePositiveInteger removeSelector: #bitOr:!
