- Pharo-dev - lists.pharo.org

[Pharo-project] compiled VM with Alien for JNIPort

by laurent laffont

Hi, is there a compiled VM available with Alien for OSX ? I want to use JNIPort. Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

May 9, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

Another that....all those incorrect compiled method has the same: they miss the bytecode 120 (self return), and they ALL have the same last byte: 32. what that 32 can be? I don't know... On Mon, May 9, 2011 at 3:27 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Ok, the problem is the following. Check my screenshot of the previous mail. > Left is incorrect, right is correct. > As you can notice, the "correct" CompiledMethod finishes with a bytecode > "return self" and number 78. This bytecode is missing in the "incorrect" CM. > And, the first byte in method trailer in the incorrect CM is 120. Guess > what? 16r78 -> 120. So...the incorrect CM interpret that byte as trailer > instead of bytecode. > Now, if you ask to the incorrect CM: "trailer data", you get, of course, > 120. > > If you see > > sourcePointer: ptr > > self clear. > data := ptr. > "see if we can encode pointer using 4-byte trailer" > kind := (ptr between: 16r1000000 and: 16r4FFFFFF) > ifTrue: [ #SourcePointer ] ifFalse: [ #VarLengthSourcePointer ]. > > > You can guess that ptr is 120, hence it sets #VarLengthSourcePointer > > Now...two problem bugs: > > 1) how can these CM be generated???? Compiler bug? > > 2) where are they kept that I cannot garbage collect them ?? > > Cheers > > Mariano > > > > On Mon, May 9, 2011 at 2:50 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Mon, May 9, 2011 at 12:48 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> the one to the left seems like broken. it not ends with return self. >>> >>> >> yes, exactly. That one on the left is the one that trailer kind answers >> #VarLengthSourcePointer >> the right is the correct one. >> >> You can also notice that the one of the left in addition to not having the >> last bytecode (self return), it has only 2 bytes for the trailer. >> >> Anyway, regardless of how such CM could have been generated, I CANNOT find >> who is pointing to them. They appear only in PharoDev and I cannot find any >> pattern between them :( >> >> :( >> >> On 9 May 2011 11:22, Mariano Martinez Peck <marianopeck(a)gmail.com> >>> wrote: >>> > >>> > >>> > On Mon, May 9, 2011 at 10:53 AM, Mariano Martinez Peck >>> > <marianopeck(a)gmail.com> wrote: >>> >> >>> >> >>> >> On Mon, May 9, 2011 at 10:27 AM, Nicolas Cellier >>> >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> >>> >>> Hi Mariano, >>> >>> you should try these two things before repeating yourself: >>> >>> >>> >>> (CompiledMethod allInstances select: [:each | each trailer kind = >>> >>> #VarLengthSourcePointer] ) first trailer kind. >>> >>> >>> >>> | temp | >>> >>> temp := (CompiledMethod allInstances select: [:each | each trailer >>> >>> kind = #VarLengthSourcePointer] ) first. >>> >>> temp == (temp methodClass >> temp selector) >>> >>> >>> >> >>> >> Thanks Nicolas. Yes, in fact all of you were right. They are not the >>> same >>> >> CM instance. They are different. >>> >> It is wierd that they are only present in Pharo1.3: >>> >> >>> >> >>> >> ((CompiledMethod allInstances select: [:each | each trailer kind = >>> >> #VarLengthSourcePointer] ) ) size >>> >> ->>> 11 >>> >> >>> >> And in Pharo 1.2, cero and and 1.1.1, 2. >>> >> >>> >> I am trying to inspect pointers to them to see who is pointing to >>> >> them...but I cannot find anything :( >>> >> >>> >> I will continue.... >>> >> >>> > >>> > More data: there are only these kind of compiled methods in the dev >>> image. >>> > Not in core. >>> > >>> > In addition, if I do: ScriptLoader new cleanUpForRelease, then inspect >>> > ((CompiledMethod allInstances select: [:each | each trailer kind = >>> > #VarLengthSourcePointer] ) ) >>> > >>> > and then I click on the first element in the inspector.... VM CRASH!!! >>> with >>> > both, InterpreterVM and CogVM. >>> > >>> > I can see the difference in the trailer of the CMs (I attach >>> screenshot), >>> > but still cannot find who is pointing to that weird instances :( >>> > >>> > grrr... thanks for the help >>> > >>> > >>> > >>> >> >>> >> thanks >>> >> >>> >> >>> >> >>> >>> It may be possible that CompiledMethod>>printString is lying to >>> you... >>> >>> >>> >>> Nicolas >>> >>> >>> >>> 2011/5/9 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> >>> > >>> >>> > >>> >>> > On Mon, May 9, 2011 at 6:14 AM, Igor Stasenko <siguctua(a)gmail.com> >>> >>> > wrote: >>> >>> >> >>> >>> >> On 9 May 2011 00:52, Mariano Martinez Peck <marianopeck(a)gmail.com >>> > >>> >>> >> wrote: >>> >>> >> > Hi guys, Maybe it is too late and I am not seeing something >>> >>> >> > obvious...so >>> >>> >> > another look is really appreciated. If I do: >>> >>> >> > >>> >>> >> > (CompiledMethod allInstances select: [:each | each trailer kind >>> = >>> >>> >> > #VarLengthSourcePointer] ) first >>> >>> >> > ---> (CodeLoader class>>#initialize "a >>> CompiledMethod(311951360)") >>> >>> >> > >>> >>> >> > But then: >>> >>> >> > >>> >>> >> > (CodeLoader class >> #initialize) trailer kind >>> >>> >> > ----> #SourcePointer >>> >>> >> > >>> >>> >> > WHYYY?? why it is answering #SourcePointer instead of >>> >>> >> > #VarLengthSourcePointer ?? >>> >>> >> > >>> >>> >> > grrr how can that be possible??? It happens the same to each of >>> the >>> >>> >> > CompiledMethods I select as #VarLengthSourcePointer. When I >>> then >>> >>> >> > ask >>> >>> >> > the >>> >>> >> > #kind they always answer #SourcePointer instead of >>> >>> >> > #VarLengthSourcePointer >>> >>> >> > >>> >>> >> is it same compiled methods? >>> >>> >> Because it is absolutely normal if they using different source >>> >>> >> pointer. >>> >>> >> >>> >>> > >>> >>> > I didn't understand your question. Yes, it is exactly the same >>> >>> > CompiledMethod. >>> >>> > Look, if I do: >>> >>> > >>> >>> > (CompiledMethod allInstances select: [:each | each trailer kind = >>> >>> > #VarLengthSourcePointer] ) first >>> >>> > >>> >>> > I get >>> >>> > ---> (CodeLoader class>>#initialize "a CompiledMethod(311951360)") >>> >>> > >>> >>> > So...it means that such CompiledMethod answers >>> #VarLengthSourcePointer >>> >>> > when >>> >>> > send "trailer kind". Ok? >>> >>> > >>> >>> > But immediatly after, if I ask the trailer kind to the SAME >>> compiled >>> >>> > method: >>> >>> > >>> >>> > (CodeLoader class >> #initialize) trailer kind >>> >>> > >>> >>> > I get >>> >>> > ----> #SourcePointer >>> >>> > >>> >>> > WHYYY?? why it is answering #SourcePointer instead of >>> >>> > #VarLengthSourcePointer ?? >>> >>> > >>> >>> >> >>> >>> >> > thanks in advance, >>> >>> >> > >>> >>> >> > -- >>> >>> >> > Mariano >>> >>> >> > http://marianopeck.wordpress.com >>> >>> >> > >>> >>> >> > >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> -- >>> >>> >> Best regards, >>> >>> >> Igor Stasenko AKA sig. >>> >>> >> >>> >>> > >>> >>> > >>> >>> > >>> >>> > -- >>> >>> > Mariano >>> >>> > http://marianopeck.wordpress.com >>> >>> > >>> >>> > >>> >>> >>> >> >>> >> >>> >> >>> >> -- >>> >> Mariano >>> >> http://marianopeck.wordpress.com >>> >> >>> > >>> > >>> > >>> > -- >>> > Mariano >>> > http://marianopeck.wordpress.com >>> > >>> > >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

Ok, the problem is the following. Check my screenshot of the previous mail. Left is incorrect, right is correct. As you can notice, the "correct" CompiledMethod finishes with a bytecode "return self" and number 78. This bytecode is missing in the "incorrect" CM. And, the first byte in method trailer in the incorrect CM is 120. Guess what? 16r78 -> 120. So...the incorrect CM interpret that byte as trailer instead of bytecode. Now, if you ask to the incorrect CM: "trailer data", you get, of course, 120. If you see sourcePointer: ptr self clear. data := ptr. "see if we can encode pointer using 4-byte trailer" kind := (ptr between: 16r1000000 and: 16r4FFFFFF) ifTrue: [ #SourcePointer ] ifFalse: [ #VarLengthSourcePointer ]. You can guess that ptr is 120, hence it sets #VarLengthSourcePointer Now...two problem bugs: 1) how can these CM be generated???? Compiler bug? 2) where are they kept that I cannot garbage collect them ?? Cheers Mariano On Mon, May 9, 2011 at 2:50 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > > > On Mon, May 9, 2011 at 12:48 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> the one to the left seems like broken. it not ends with return self. >> >> > yes, exactly. That one on the left is the one that trailer kind answers > #VarLengthSourcePointer > the right is the correct one. > > You can also notice that the one of the left in addition to not having the > last bytecode (self return), it has only 2 bytes for the trailer. > > Anyway, regardless of how such CM could have been generated, I CANNOT find > who is pointing to them. They appear only in PharoDev and I cannot find any > pattern between them :( > > :( > > On 9 May 2011 11:22, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> > >> > >> > On Mon, May 9, 2011 at 10:53 AM, Mariano Martinez Peck >> > <marianopeck(a)gmail.com> wrote: >> >> >> >> >> >> On Mon, May 9, 2011 at 10:27 AM, Nicolas Cellier >> >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> >> >>> Hi Mariano, >> >>> you should try these two things before repeating yourself: >> >>> >> >>> (CompiledMethod allInstances select: [:each | each trailer kind = >> >>> #VarLengthSourcePointer] ) first trailer kind. >> >>> >> >>> | temp | >> >>> temp := (CompiledMethod allInstances select: [:each | each trailer >> >>> kind = #VarLengthSourcePointer] ) first. >> >>> temp == (temp methodClass >> temp selector) >> >>> >> >> >> >> Thanks Nicolas. Yes, in fact all of you were right. They are not the >> same >> >> CM instance. They are different. >> >> It is wierd that they are only present in Pharo1.3: >> >> >> >> >> >> ((CompiledMethod allInstances select: [:each | each trailer kind = >> >> #VarLengthSourcePointer] ) ) size >> >> ->>> 11 >> >> >> >> And in Pharo 1.2, cero and and 1.1.1, 2. >> >> >> >> I am trying to inspect pointers to them to see who is pointing to >> >> them...but I cannot find anything :( >> >> >> >> I will continue.... >> >> >> > >> > More data: there are only these kind of compiled methods in the dev >> image. >> > Not in core. >> > >> > In addition, if I do: ScriptLoader new cleanUpForRelease, then inspect >> > ((CompiledMethod allInstances select: [:each | each trailer kind = >> > #VarLengthSourcePointer] ) ) >> > >> > and then I click on the first element in the inspector.... VM CRASH!!! >> with >> > both, InterpreterVM and CogVM. >> > >> > I can see the difference in the trailer of the CMs (I attach >> screenshot), >> > but still cannot find who is pointing to that weird instances :( >> > >> > grrr... thanks for the help >> > >> > >> > >> >> >> >> thanks >> >> >> >> >> >> >> >>> It may be possible that CompiledMethod>>printString is lying to you... >> >>> >> >>> Nicolas >> >>> >> >>> 2011/5/9 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> > >> >>> > >> >>> > On Mon, May 9, 2011 at 6:14 AM, Igor Stasenko <siguctua(a)gmail.com> >> >>> > wrote: >> >>> >> >> >>> >> On 9 May 2011 00:52, Mariano Martinez Peck <marianopeck(a)gmail.com> >> >>> >> wrote: >> >>> >> > Hi guys, Maybe it is too late and I am not seeing something >> >>> >> > obvious...so >> >>> >> > another look is really appreciated. If I do: >> >>> >> > >> >>> >> > (CompiledMethod allInstances select: [:each | each trailer kind >> = >> >>> >> > #VarLengthSourcePointer] ) first >> >>> >> > ---> (CodeLoader class>>#initialize "a >> CompiledMethod(311951360)") >> >>> >> > >> >>> >> > But then: >> >>> >> > >> >>> >> > (CodeLoader class >> #initialize) trailer kind >> >>> >> > ----> #SourcePointer >> >>> >> > >> >>> >> > WHYYY?? why it is answering #SourcePointer instead of >> >>> >> > #VarLengthSourcePointer ?? >> >>> >> > >> >>> >> > grrr how can that be possible??? It happens the same to each of >> the >> >>> >> > CompiledMethods I select as #VarLengthSourcePointer. When I then >> >>> >> > ask >> >>> >> > the >> >>> >> > #kind they always answer #SourcePointer instead of >> >>> >> > #VarLengthSourcePointer >> >>> >> > >> >>> >> is it same compiled methods? >> >>> >> Because it is absolutely normal if they using different source >> >>> >> pointer. >> >>> >> >> >>> > >> >>> > I didn't understand your question. Yes, it is exactly the same >> >>> > CompiledMethod. >> >>> > Look, if I do: >> >>> > >> >>> > (CompiledMethod allInstances select: [:each | each trailer kind = >> >>> > #VarLengthSourcePointer] ) first >> >>> > >> >>> > I get >> >>> > ---> (CodeLoader class>>#initialize "a CompiledMethod(311951360)") >> >>> > >> >>> > So...it means that such CompiledMethod answers >> #VarLengthSourcePointer >> >>> > when >> >>> > send "trailer kind". Ok? >> >>> > >> >>> > But immediatly after, if I ask the trailer kind to the SAME compiled >> >>> > method: >> >>> > >> >>> > (CodeLoader class >> #initialize) trailer kind >> >>> > >> >>> > I get >> >>> > ----> #SourcePointer >> >>> > >> >>> > WHYYY?? why it is answering #SourcePointer instead of >> >>> > #VarLengthSourcePointer ?? >> >>> > >> >>> >> >> >>> >> > thanks in advance, >> >>> >> > >> >>> >> > -- >> >>> >> > Mariano >> >>> >> > http://marianopeck.wordpress.com >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> >> >>> >> >> >>> >> -- >> >>> >> Best regards, >> >>> >> Igor Stasenko AKA sig. >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Mariano >> >>> > http://marianopeck.wordpress.com >> >>> > >> >>> > >> >>> >> >> >> >> >> >> >> >> -- >> >> Mariano >> >> http://marianopeck.wordpress.com >> >> >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] How to load Nautilus?

by Benjamin

Now ConfigurationOfNautilus loads RPackage. On the last 1.3 core image: Gofer new squeaksource: 'Nautilus'; package: 'ConfigurationOfNautilus'; load. ConfigurationOfNautilus loadDefault It works ^^ Ben On May 9, 2011, at 11:51 AM, Mariano Martinez Peck wrote: > > > On Mon, May 9, 2011 at 11:46 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > On May 7, 2011, at 10:46 PM, Mariano Martinez Peck wrote: > >> I took the latest PharoCore 1.3 and evaluated: >> >> Gofer new >> squeaksource: 'Nautilus'; >> package: 'ConfigurationOfNautilus'; >> load. >> >> >> ConfigurationOfNautilus project lastVersion load >> >> >> But it says >> >> This package depends on the following classes: >> SystemAnnouncer >> You must resolve these dependencies before you will be able to load these definitions: >> GroupAnnouncer >> >> >> Select Proceed to continue, or close this window to cancel the operation. >> >> >> >> Then after in the load, I have a DNU in MCWorkingCopy >> modified: aBooleanm, because MonticelloAnnouncer is nil (not defined) >> >> So....how I am supposed to load Nautilus? > > Nautilus is based on RPackage so: > > - dl PharoCore 1.3 from Hudson > - load RPackage 3.0 > - load Nautilus (stable or default, should be the same) > > Here it works > > > But the idea is that it works outside your pc ;) > > So...if Nautilus is based on RPackage, then you must add it to ConfigurationOfNautilus as a depdeny. Otherwise, I cannot guess that you need RPackage. If fact, I didn'tknow until now. > I don't know where RPackage is, nor which group should I load. > > :) > > > >> >> And if I want the integration with Refactoring Browser, OCompletion, Shout, etc, what should I do? load those packages and magically Nautilus will work ? > > OCompletion and Shout normally impact only the textMorph. > I haven't test OCompletion (I do not use it, but I will do it right now), but for Shout, load the Shout package, and no, it's not magic, but Nautilus works. > > ok cool > > > For refactoring browser, since Nautilus is based on BrowserEnvironment, it should work too. But I have to check and steal some menu's entries from OB. > > > Cool. I think this is really important :) > >> What happens if I load Nautilus in a dev image? > > No idea, let's try :) > > > Ben > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 9, 2011

[Pharo-project] [update 1.3] #13186

by Marcus Denker

13186 ----- Issue 3233: Tests for WeakSet Issue 4169: FlatMessageListBrowser has undeclared ivar title -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 9, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

On Mon, May 9, 2011 at 12:48 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > the one to the left seems like broken. it not ends with return self. > > yes, exactly. That one on the left is the one that trailer kind answers #VarLengthSourcePointer the right is the correct one. You can also notice that the one of the left in addition to not having the last bytecode (self return), it has only 2 bytes for the trailer. Anyway, regardless of how such CM could have been generated, I CANNOT find who is pointing to them. They appear only in PharoDev and I cannot find any pattern between them :( :( On 9 May 2011 11:22, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > > > On Mon, May 9, 2011 at 10:53 AM, Mariano Martinez Peck > > <marianopeck(a)gmail.com> wrote: > >> > >> > >> On Mon, May 9, 2011 at 10:27 AM, Nicolas Cellier > >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: > >>> > >>> Hi Mariano, > >>> you should try these two things before repeating yourself: > >>> > >>> (CompiledMethod allInstances select: [:each | each trailer kind = > >>> #VarLengthSourcePointer] ) first trailer kind. > >>> > >>> | temp | > >>> temp := (CompiledMethod allInstances select: [:each | each trailer > >>> kind = #VarLengthSourcePointer] ) first. > >>> temp == (temp methodClass >> temp selector) > >>> > >> > >> Thanks Nicolas. Yes, in fact all of you were right. They are not the > same > >> CM instance. They are different. > >> It is wierd that they are only present in Pharo1.3: > >> > >> > >> ((CompiledMethod allInstances select: [:each | each trailer kind = > >> #VarLengthSourcePointer] ) ) size > >> ->>> 11 > >> > >> And in Pharo 1.2, cero and and 1.1.1, 2. > >> > >> I am trying to inspect pointers to them to see who is pointing to > >> them...but I cannot find anything :( > >> > >> I will continue.... > >> > > > > More data: there are only these kind of compiled methods in the dev > image. > > Not in core. > > > > In addition, if I do: ScriptLoader new cleanUpForRelease, then inspect > > ((CompiledMethod allInstances select: [:each | each trailer kind = > > #VarLengthSourcePointer] ) ) > > > > and then I click on the first element in the inspector.... VM CRASH!!! > with > > both, InterpreterVM and CogVM. > > > > I can see the difference in the trailer of the CMs (I attach screenshot), > > but still cannot find who is pointing to that weird instances :( > > > > grrr... thanks for the help > > > > > > > >> > >> thanks > >> > >> > >> > >>> It may be possible that CompiledMethod>>printString is lying to you... > >>> > >>> Nicolas > >>> > >>> 2011/5/9 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >>> > > >>> > > >>> > On Mon, May 9, 2011 at 6:14 AM, Igor Stasenko <siguctua(a)gmail.com> > >>> > wrote: > >>> >> > >>> >> On 9 May 2011 00:52, Mariano Martinez Peck <marianopeck(a)gmail.com> > >>> >> wrote: > >>> >> > Hi guys, Maybe it is too late and I am not seeing something > >>> >> > obvious...so > >>> >> > another look is really appreciated. If I do: > >>> >> > > >>> >> > (CompiledMethod allInstances select: [:each | each trailer kind = > >>> >> > #VarLengthSourcePointer] ) first > >>> >> > ---> (CodeLoader class>>#initialize "a CompiledMethod(311951360)") > >>> >> > > >>> >> > But then: > >>> >> > > >>> >> > (CodeLoader class >> #initialize) trailer kind > >>> >> > ----> #SourcePointer > >>> >> > > >>> >> > WHYYY?? why it is answering #SourcePointer instead of > >>> >> > #VarLengthSourcePointer ?? > >>> >> > > >>> >> > grrr how can that be possible??? It happens the same to each of > the > >>> >> > CompiledMethods I select as #VarLengthSourcePointer. When I then > >>> >> > ask > >>> >> > the > >>> >> > #kind they always answer #SourcePointer instead of > >>> >> > #VarLengthSourcePointer > >>> >> > > >>> >> is it same compiled methods? > >>> >> Because it is absolutely normal if they using different source > >>> >> pointer. > >>> >> > >>> > > >>> > I didn't understand your question. Yes, it is exactly the same > >>> > CompiledMethod. > >>> > Look, if I do: > >>> > > >>> > (CompiledMethod allInstances select: [:each | each trailer kind = > >>> > #VarLengthSourcePointer] ) first > >>> > > >>> > I get > >>> > ---> (CodeLoader class>>#initialize "a CompiledMethod(311951360)") > >>> > > >>> > So...it means that such CompiledMethod answers > #VarLengthSourcePointer > >>> > when > >>> > send "trailer kind". Ok? > >>> > > >>> > But immediatly after, if I ask the trailer kind to the SAME compiled > >>> > method: > >>> > > >>> > (CodeLoader class >> #initialize) trailer kind > >>> > > >>> > I get > >>> > ----> #SourcePointer > >>> > > >>> > WHYYY?? why it is answering #SourcePointer instead of > >>> > #VarLengthSourcePointer ?? > >>> > > >>> >> > >>> >> > thanks in advance, > >>> >> > > >>> >> > -- > >>> >> > Mariano > >>> >> > http://marianopeck.wordpress.com > >>> >> > > >>> >> > > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> Best regards, > >>> >> Igor Stasenko AKA sig. > >>> >> > >>> > > >>> > > >>> > > >>> > -- > >>> > Mariano > >>> > http://marianopeck.wordpress.com > >>> > > >>> > > >>> > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] Issue in loading SqueakDBX Patch

by Mariano Martinez Peck

On Mon, May 9, 2011 at 2:27 PM, sourav roy <sourav_pharo(a)in.com> wrote: > Hi > > I have noticed that when I load the patch * > SqueakDBX-Smalltalk-Dialect-MarianoMartinezPeck.5*, > Hi. Just a litte comment. They are not called path, just packages. In fact, *SqueakDBX-Smalltalk-Dialect *is the name of the package and *SqueakDBX-Smalltalk-Dialect-MarianoMartinezPeck.5 *a particular version of such package. > the class *SqueakDBXSmalltalkDialect* does not contain any methods in the > system window. > yes it does. Check class side ;) > Is this might be the cause of the error when I load the patch *SqueakDBX-Dialect-Squeak-MarianoMartinezPeck.6 > *into pharo which has dependency on *SqueakDBXSmalltalkDialect and > OpenDBX.* > Check ConfigurationOfSqueakDBX method #baseline12: to see the dependencies (using the method #requires: Cheers Mariano > Thanks > > Sourav > > > ---------- Original message ---------- > From:""sourav roy""< sourav_pharo(a)in.com > > Date: 9 May 11 17:00:21 > Subject: Re: [Pharo-project] Issue in loading SqueakDBX Patch > To: marianopeck(a)gmail.com; "pharo-project" < > pharo-project(a)lists.gforge.inria.fr> > > > Hi, > > I loaded the following patches in pharo 1.2.1 which i downloaded from > http://www.squeaksource.com/SqueakDBX. > > -ConfigurationOfSqueakDBX-MarianoMartinezPeck.8 > -penDBX-Core-MarianoMartinezPeck.256 > -queakDBX-Dialect-Squeak-MarianoMartinezPeck.3 > -queakDBX-Smalltalk-Dialect-MarianoMartinezPeck.5 > > Please advice me if am wrong and suggest me the correct method for it. I am > not able to load it through Gofer as am working in a secured environment. > > Thanks, > > Sourav > > > ---------- Original message ---------- > From:"Mariano Martinez Peck"< marianopeck(a)gmail.com > > Date: 9 May 11 14:55:24 > Subject: Re: [Pharo-project] Issue in loading SqueakDBX Patch > To: Pharo-project(a)lists.gforge.inria.fr; > > Hi....that's weird. Could you tell me please how did you exactly install > SqueakDBX? > > > > On Mon, May 9, 2011 at 11:19 AM, sourav roy <sourav_pharo(a)in.com> wrote: > >> >> Hi All, >> >> I am getting some error while loading a SqueakDBX patch in Pharo 1.2.1. >> Please see the below screen shot attcahed and advice >> >> *Thanks,* >> >> *Sourav Roy| Bangalore|INDIA * >> >> >> ------------------------------ >> ::DISCLAIMER:: >> >> ----------------------------------------------------------------------------------------------------------------------- >> >> The contents of this e-mail and any attachment(s) are confidential and >> intended for the named recipient(s) only. >> It shall not attach any liability on the originator or HCL or its >> affiliates. Any views or opinions presented in >> this email are solely those of the author and may not necessarily reflect >> the opinions of HCL or its affiliates. >> Any form of reproduction, dissemination, copying, disclosure, >> modification, distribution and / or publication of >> this message without the prior written consent of the author of this >> e-mail is strictly prohibited. If you have >> received this email in error please delete it and notify the sender >> immediately. Before opening any mail and >> attachments please check them for viruses and defect. >> >> ---------------------------------------------------------- >> ------------------------------------------------------------- >> >> > > Dear *pharo-project !* Get Yourself a cool, short *(a)in.com* Email ID now!<http://secure.in.com/sso/commonreg.php?utm_source=invite&utm_medium=outgoing> > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > Get Yourself a cool, short *(a)in.com* Email ID now!<http://mail.in.com/mails/new_reg.php?utm_source=invite&utm_medium=outgoing> > > > Get Yourself a cool, short *(a)in.com* Email ID now!<http://mail.in.com/mails/new_reg.php?utm_source=invite&utm_medium=outgoing> > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] Issue in loading SqueakDBX Patch

by Mariano Martinez Peck

On Mon, May 9, 2011 at 1:30 PM, sourav roy <sourav_pharo(a)in.com> wrote: > > Hi, > > I loaded the following patches in pharo 1.2.1 which i downloaded from > http://www.squeaksource.com/SqueakDBX. > > -ConfigurationOfSqueakDBX-MarianoMartinezPeck.8 > -penDBX-Core-MarianoMartinezPeck.256 > -queakDBX-Dialect-Squeak-MarianoMartinezPeck.3 > -queakDBX-Smalltalk-Dialect-MarianoMartinezPeck.5 > > Loading that is not correct because: 1) the order is not correct (for example SqueakDBX-Smalltalk-Dialect should be first than SqueakDBX-Dialect-Squeak) 2) you are not loading SqueakDBX dependencies like FFI (and in fact the sintax error you have is because you are not loading FFI). To solves those issues, we have a Metacello configuration. Gofer has nothing to do with a secured environment or not: all you have to do is to load the package ConfigurationOfSqueakDBX. No matter how: you can use the following Gofer script: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSqueakDBX'; load. Or, open a Monticello Browser, -> add repository -> www.squeaksource.com/MetacelloRepository -> select ConfiguratonOfSqueakDBX -> load. Once you have download ConfigurationOfSqueakDBX all you have to do is: (ConfigurationOfSqueakDBX project version: #stable) load. I *really* recommend you to read the Metacello chapter of Pharo By Example, since all this is explained there: https://gforge.inria.fr/frs/download.php/28462/Metacello.pdf Cheers Mariano > Please advice me if am wrong and suggest me the correct method for it. I am > not able to load it through Gofer as am working in a secured environment. > > Thanks, > > Sourav > > > ---------- Original message ---------- > From:"Mariano Martinez Peck"< marianopeck(a)gmail.com > > Date: 9 May 11 14:55:24 > Subject: Re: [Pharo-project] Issue in loading SqueakDBX Patch > To: Pharo-project(a)lists.gforge.inria.fr; > > Hi....that's weird. Could you tell me please how did you exactly install > SqueakDBX? > > > > On Mon, May 9, 2011 at 11:19 AM, sourav roy <sourav_pharo(a)in.com> wrote: > >> >> Hi All, >> >> I am getting some error while loading a SqueakDBX patch in Pharo 1.2.1. >> Please see the below screen shot attcahed and advice >> >> *Thanks,* >> >> *Sourav Roy| Bangalore|INDIA * >> >> >> ------------------------------ >> ::DISCLAIMER:: >> >> ----------------------------------------------------------------------------------------------------------------------- >> >> The contents of this e-mail and any attachment(s) are confidential and >> intended for the named recipient(s) only. >> It shall not attach any liability on the originator or HCL or its >> affiliates. Any views or opinions presented in >> this email are solely those of the author and may not necessarily reflect >> the opinions of HCL or its affiliates. >> Any form of reproduction, dissemination, copying, disclosure, >> modification, distribution and / or publication of >> this message without the prior written consent of the author of this >> e-mail is strictly prohibited. If you have >> received this email in error please delete it and notify the sender >> immediately. Before opening any mail and >> attachments please check them for viruses and defect. >> >> ---------------------------------------------------------- >> ------------------------------------------------------------- >> >> > > Dear *pharo-project !* Get Yourself a cool, short *(a)in.com* Email ID now!<http://secure.in.com/sso/commonreg.php?utm_source=invite&utm_medium=outgoing> > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > Get Yourself a cool, short *(a)in.com* Email ID now!<http://mail.in.com/mails/new_reg.php?utm_source=invite&utm_medium=outgoing> > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-project] Issue in loading SqueakDBX Patch

by sourav roy

HiI have noticed that when I load the patch SqueakDBXSmalltalkDialectMarianoMartinezPeck.5, the class SqueakDBXSmalltalkDialect does not contain any methods in the system window. Is this might be the cause of the error when I load the patch SqueakDBXDialectSqueakMarianoMartinezPeck.6 into pharo which has dependency on SqueakDBXSmalltalkDialect and OpenDBX. Thanks Sourav Original message From:""sourav roy""< souravpharo(a)in.com >Date: 9 May 11 17:00:21Subject: Re: [Pharoproject] Issue in loading SqueakDBX PatchTo: marianopeck(a)gmail.com; "pharoproject" Hi, I loaded the following patches in pharo 1.2.1 which i downloaded from http://www.squeaksource.com/SqueakDBX. ConfigurationOfSqueakDBXMarianoMartinezPeck.8penDBXCoreMarianoMartinezPeck.256queakDBXDialectSqueakMarianoMartinezPeck.3queakDBXSmalltalkDialectMarianoMartinezPeck.5 Please advice me if am wrong and suggest me the correct method for it. I am not able to load it through Gofer as am working in a secured environment. Than ks, Sourav Original message From:"Mariano Martinez Peck"< marianopeck(a)gmail.com >Date: 9 May 11 14:55:24Subject: Re: [Pharoproject] Issue in loading SqueakDBX PatchTo: Pharoproject@lists.gforge.inria.fr;Hi....that's weird. Could you tell me please how did you exactly install SqueakDBX?On Mon, May 9, 2011 at 11:19 AM, sourav roywrote:Hi All, I am getting some error while loading a SqueakDBX patch in Pharo 1.2.1. Please see the below screen shot attcahed and adviceThanks, Sourav Roy| Bangalore|INDIA::DISCLAIMER::The contents of this email and any attachment(s) are confidential and intended for the named recipient(s) only.It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented inthis email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication ofthis message without the prior written consent of the author of this email is strictly prohibited. If you havereceived this email in error please delete it and notify the sender immediately. Before opening any mail andattachments please check them for viruses and defect. Dear pharoproject ! Get Yourself a cool, short @in.com Email ID now! Marianohttp://marianopeck.wordpress.com Get Yourself a cool, short @in.com Email ID now!Get Yourself a cool, short @in.com Email ID now!

May 9, 2011

Re: [Pharo-project] OB variable references browser bug [fix]

by Igor Stasenko

OH, forgot to mention. This in Pharo 1.3 image. On 9 May 2011 13:11, Igor Stasenko <siguctua(a)gmail.com> wrote: > There is a DNU in OB, > when you do following: > > - go to some class > - click its 'variables' , to open variable references browser > - select any variable and go to one of the methods which using it > - modify this method to no longer reference that variable and accept it. > > And at that moment you got DNU. > > The possible fix is attached. But note, that this method actually > invoked as a result of handing another error. > I don't know, maybe it would be better to prevent an original error > from occur, rather than putting a workaround like this. > I'm not an expert in OB, so i just fixed so it kinda works, at least > its not triggers DNU anymore. > > To see the original error, simply put 'self halt' in the method i > attached, and then look at the stack in debugger. > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

May 9, 2011