Torsten and JB: it would be cool to create a new metacello configuration version with this new version of VMMaker, puting the fix about the baseHeaderSize and integrating JB fixes to VMMaker.
Cheers Mariano On Tue, Feb 23, 2010 at 7:55 AM, Fernando olivero <[email protected]>wrote: > > On Feb 23, 2010, at 4:19 AM, John M McIntosh wrote: > > > > > On 2010-02-22, at 6:48 PM, Javier Pimás wrote: > > > >> > > > >> Lastly, as I said when I loaded Alien Core the first time, I got this > error while loading it: > >> > >> Alien class>>#ensureInSpecialObjectsArray: "Index probably wrong". > >> > >> What should I do about that? ignore it? > > > > Well it seems to be related to > > > > ((Smalltalk includesKey: #ObjectMemory) > > and: [((Smalltalk at: #ObjectMemory) classPool at: #ClassAlien > ifAbsent: []) ~~ (index - 1)]) ifTrue: > > [self error: 'index probably wrong']. > > > > Usually people don't have ObjectMemory loaded in their image, and I"m not > sure what it is check for. > > Why don't you try it in a regular Pharo image versus your VMMaker image. > > Great work Jorge! Nice to know you won the battle against VMMaker! > > The ensure in special objects array error, has to do with some missing > classes as John pointed out. > > The smalltalk special objects array has hardcoded indexes for some relevant > classes ( Globals) in the system. > In the alien configuration i've just ensured that the size should be 53, > before loading Alien, because the Alien code installs itself in that array > at positions 54 and 55. > > > > _______________________________________________ > 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
