yes it would be good. Stef
On Dec 5, 2010, at 10:37 PM, Mariano Martinez Peck wrote: > marcus, maybe we can fix this for the one clicks? > > cheers > > mariano > > On Sun, Dec 5, 2010 at 10:12 PM, jaayer <[email protected]> wrote: > > > > > ---- On Sun, 05 Dec 2010 12:55:17 -0800 Igor Stasenko wrote ---- > > >On 5 December 2010 20:53, jaayer wrote: > >> > >> > >> I have found that I cannot save any package to any repository (local or > >> Squeaksource) using Pharo 1.1.1 with the CogVM on 64-bit Ubuntu 10.10. > >> After being prompted to describe the changes to the package and then > >> accepting, the entire image just crashes with the stack dump below. I do > >> have the proper IA32-libs installed (to run 32-bit applications on a > >> 64-bit Linux), and everything else seems to work fine, including loading > >> of Monticello packages. > >> > >> This code: "UUID new primMakeUUID" can produce the crash. Changing > >> UUID>>primMakeUUID to use the non-primitive implementation: > >> UUIDGenerator default generateBytes: self forVersion: 4. > >> stops the crashing. > >> > > > >UUID bug is well known for a long time. > >It is plaguing us for 2 years i think. > > I see, my mistake. I assumed it was new because this is the first time I have > ever encountered it on Linux after two years of using Pharo, and there were > no recent posts here discussing it (though searching just now, I found a > thread concerning Cog and UUID crashes from last October) or related issues > in the tracker that I could find. But I feel compelled to stress that the > current Pharo 1.1.1 OneClick distribution is shipping with this bug in it, > and the previous 1.1 distribution did not. Perhaps this quarrelsome plug-in > should be disabled by default, if only on Linux. I would hate for a budding > Pharo user to encounter this while going through the exercises in Pharo By > Example. > > >-- > >Best regards, > >Igor Stasenko AKA sig. > > > > > > >
