> Hi,
>
> If you take the latest Pharo 2.0 image from Jenkins (20059) and you execute
> the expression:
>
> (Metaclass allInstances select: [:c | c superclass = ProtoObject class])
> inspect
>
> you will get an collection inspector where the first object is very strange
> one. It is very hard to get any useful information about the origin of this
> evil object. The only thing we know exactly is that it causes virtual machine
> segmentation faults while trying to export class ScrollBar via Fuel. Not only
> CogVM but even StackVM.
>
> Can you, please, try to help us to get as much information as possible about
> this object? I named it "dzindzik" :-)
>
> Cheers,
> -- Pavel
In 20060
I got 4 elements and the first one is apparently Metaclass but I do not
understand why
self first class
Metaclass
self first class superclass
ClassDescription
Now I do not understand why this guy cannot get printed.
I do not see why
ClassDescription>>printOn: aStream
aStream nextPutAll: self name
Metaclass>>name
"Answer a String that is the name of the receiver, either 'Metaclass'
or
the name of the receiver's class followed by ' class'."
thisClass == nil
ifTrue: [^'a Metaclass']
ifFalse: [^thisClass name , ' class']
self first soleInstance printString
-> leads to have emergency debugger.
Stef
