Ok now I understand your email :) Sorry too early form my braincells.
The problem is that I could not harvest a fix for 3.9.1.
I did all the work but apparently the update could not find it because
the release team of 3.10 did not let enough
numbers for updates. I asked for help but got no feedback. So I gave
up. Sad.
0006834: Delay class>>timeoutSemaphore:afterMSecs: doesn t.
Description The implementation for Delay
class>>timeoutSemaphore:afterMSecs: doesn t even use its first
parameter, so it can t do what it says it does.
http://bugs.squeak.org/view.php?id=6834
Stef
On Jun 29, 2008, at 12:06 AM, Hilaire Fernandes wrote:
With the last Magma beta (41beta3, 41beta4), I have noted a strange
problem when I start a Magma server instance. The image got lock up by
a semaphore at the initialization phase of the Magma server.
The morph interface is locked, I can get control with [Alt]+. See
screenshot
From the debugger, clicking Proceed resumes normally the execution,
and the Magma server is finally started.
This happens with 3.9.1, but not with 3.9, nor last pharo will all
update.
Is it related to fix applied to 3.9.1 as
http://bugs.squeak.org/view.php?id=6588
or http://bugs.squeak.org/view.php?id=6581
I was beliving pharo was based on 3.9.1,so I am curious why Magma
server works with it.
Any tips
Hilaire
--
http://blog.ofset.org/hilaire
<magma-semaphore.png>_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
