thank you, version 51 is already infected. Has anyone some build between?

-- Pavel

On Wed, May 9, 2012 at 1:47 PM, Francisco Garau
<[email protected]> wrote:
> Evaluating your code in #build 2041 returns only the 3 expected classes:
>
> (Metaclass allInstances select: [:c | c superclass = ProtoObject class])
> inspect
> =>
> {Object class. MessageCatcher class. TestCoverage class}
>
>
> On 9 May 2012 12:35, Pavel Krivanek <[email protected]> wrote:
>>
>> I had the same idea but the build history is quite short (7) and with
>> our updating speed it is filled within two days :-) I extended the
>> builds count yesterday to 20.
>>
>> The next interesting information about dzindizik:
>>
>> o := ((Metaclass allInstances detect: [:c | c superclass = ProtoObject
>> class]) instVarNamed: #thisClass). 1. "number here to avoid printing".
>>
>> Smalltalk allClasses select: [:c | o isKindOf: c] -> an
>> OrderedCollection(Behavior Class ClassDescription Object ProtoObject)
>>
>> Smalltalk allClasses select: [:c | o class == c] -> an OrderedCollection()
>>
>> It looks like a subclass of Class :-)
>>
>> -- Pavel
>>
>> On Wed, May 9, 2012 at 1:24 PM, Herby Vojčík <[email protected]> wrote:
>> > Hi,
>> >
>> > just an idea: maybe bisecting and finding which update brought it in and
>> > then analyzing its changes may help... or you know it is 20059?
>> >
>> > Herby
>> >
>> >
>> > Pavel Krivanek wrote:
>> >>
>> >> 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
>> >
>> >
>>
>

Reply via email to