- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Strangest object ever seen?

by Pavel Krivanek

On Wed, May 9, 2012 at 2:38 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > > > Pavel Krivanek wrote: >> >> Some next interesting information: >> >> o := ((Metaclass allInstances detect: [:c | c superclass = ProtoObject >> class]) instVarNamed: #thisClass). 1. >> >> Smalltalk allClassesAndTraits select: [:c | o isKindOf: c] -> Â an >> OrderedCollection(Behavior Class ClassDescription Object ProtoObject) >> >> Smalltalk allClasses select: [:c | o class == c] -> Â an >> OrderedCollection() Â "WTF" > > > My gut feeling says 'o class == o' here. > Also it may be interesting to see what is o class class. > (o class is not inspectable, is it?) As I see there is a circle but different one: dzindzik := (Metaclass allInstances detect: [:c | c superclass = ProtoObject class]). 1. o := dzindzik instVarNamed: #thisClass. 1. o class == dzindzik -> true -- Pavel > Herby > >

May 9, 2012

Re: [Pharo-project] DrGeo Android release

by Douglas Brebner

On 09/05/2012 08:42, Hilaire Fernandes wrote: > Hello, > > A small note to let you know we release a free version of DrGeo on > Google Play. > > https://play.google.com/store/apps/details?id=eu.drgeo.android > > +1 for Smalltalk :) > It works quite nicely on my Galaxy SII phone. Congratulations :)

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Herby VojÄÃk

Pavel Krivanek wrote: > Some next interesting information: > > o := ((Metaclass allInstances detect: [:c | c superclass = ProtoObject > class]) instVarNamed: #thisClass). 1. > > Smalltalk allClassesAndTraits select: [:c | o isKindOf: c] -> an > OrderedCollection(Behavior Class ClassDescription Object ProtoObject) > > Smalltalk allClasses select: [:c | o class == c] -> an > OrderedCollection() "WTF" My gut feeling says 'o class == o' here. Also it may be interesting to see what is o class class. (o class is not inspectable, is it?) Herby

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Pavel Krivanek

Some next interesting information: o := ((Metaclass allInstances detect: [:c | c superclass = ProtoObject class]) instVarNamed: #thisClass). 1. Smalltalk allClassesAndTraits select: [:c | o isKindOf: c] -> an OrderedCollection(Behavior Class ClassDescription Object ProtoObject) Smalltalk allClasses select: [:c | o class == c] -> an OrderedCollection() "WTF" o subclasses -> #Object "WTF!" o subclasses class -> ByteSymbol "WTF!! should be Array" o superclass -> ProtoObject "WTF" (o methodDict keys asSortedCollection first: 50) = (Object methodDict keys asSortedCollection first: 50) -> true "wasn't it Object in better times?" -- Pavel On Wed, May 9, 2012 at 1:35 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> 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 <herby(a)mailbox.sk> 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 >> >>

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Pavel Krivanek

thank you, version 51 is already infected. Has anyone some build between? -- Pavel On Wed, May 9, 2012 at 1:47 PM, Francisco Garau <francisco.garau(a)gmail.com> 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 <pavel.krivanek(a)gmail.com> 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 <herby(a)mailbox.sk> 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 >> > >> > >> >

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Francisco Garau

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 <pavel.krivanek(a)gmail.com> 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 <herby(a)mailbox.sk> 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 > > > > > >

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Pavel Krivanek

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 <herby(a)mailbox.sk> 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 > >

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Herby VojÄÃk

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

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Pavel Krivanek

On Wed, May 9, 2012 at 9:07 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> 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 > > 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. self name shows: a Dictionary(#DependentsFields->a WeakIdentityKeyDictionary(a CategoryWidget->a DependentsArray(a PluggableIconListMorph(217841664)) a ContextVariablesInspector->a DependentsArray(a PluggableListMorph(445382656) a PluggableTextMorph(1046216704)) a ContextVariablesInspector->a DependentsArray(a PluggableListMorph(290193408) ... ) The source of printing problems will be in thisClass. The next interesting thing is that it has no pointers and it is removed after garbageCollect. -- Pavel > Stef > > > > >

May 9, 2012

[Pharo-project] tentative schedule for the pharo conference

by StÃ©phane Ducasse

Hi guys Here is a tentative schedule for the forth coming conference. ICAL: https://www.google.com/calendar/ical/2d97rjlqso704v09d49sgcsjec%40group.cal… HTML: https://www.google.com/calendar/embed?src=2d97rjlqso704v09d49sgcsjec%40grou… please lets us know if you have any idea feedback. -- Sef

May 9, 2012