My guess is that there are duration instances around (from OB or from Universes) that break when their methods are updated in a bad order. When you first update the core image to 10203 and then load OB, everything seems ok.
The problematic change is in Duration/Time: http://code.google.com/p/pharo/issues/detail?can=1&q=101 from http://bugs.squeak.org/view.php?id=4669 This is a change that was also applied to 3.10. Adrian On Jan 8, 2009, at 09:21 , Stéphane Ducasse wrote: > I can even reproduce it. > take 10202 > ScriptLoader loadOB > update > -> crashes > > > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511301088 >> seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300996 >> days:hours:minutes:seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300892 >> seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300800 >> days:hours:minutes:seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300696 >> seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300604 >> days:hours:minutes:seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300500 >> seconds:nanoSeconds: > 1/8/09 8:58:20 AM [0x0-0x1b01b0].org.squeak.Squeak[6236] 511300408 >> days:hours:minutes:seconds:nanoSeconds: > > stef > > _______________________________________________ > 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
