- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Time to rename copyWithTrailerBytes: ?

by Igor Stasenko

On 10 May 2011 12:35, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > If I understand correctly, before the trailers we used to use just an array > of bytes...now we use a CompiledMethodTrailer. So, the method > copyWithTrailerBytes:Â is misleading. > yes. it should be named copyWithTrailer: instead, but since at the time i introducing trailers there was only bytes, i had to preserve the name for compatibility (among other things). Btw, if you look at CompiledMethod, there's a lot of things which can be cleaned-up/refactored. For example all code which managing sourcePointer(s) and SourceFiles, not belongs to CompiledMethod. It should reside somewhere in SourceFileArray (or its subclass). > cheers > > -- > Mariano > http://marianopeck.wordpress.com > > -- Best regards, Igor Stasenko AKA sig.

May 10, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

> > > > > I must be wrong, because the dev image when it is build, it calls all > > cleanUp methods for classes, so CompiledMethod class >> cleanUp shuld > have > > been called, but if I take the Pharo1.3 result, I can see the source code > > (not decompiled) > > > > But you can't see the source of those methods in browser, because > browser works only with installed methods > while cleanup touching only non-installed ones. > grrrr sorry, I forgot about the #isInstalled ... I went directly to see #destroySourcePointer heheheh > > >> > >> When i do this, my image hangs. > > > > I have just tried and it crash!!! Actually, I evaluated CompiledMethod > > cleanUp. And just after cmd+b in CompiledMethod (to browse it) -> crash > > How it is possilbe it didn't crash while building the dev image? or the > > first time I browse a class? > > maybe this incorrect CM are created by the build process just after the > > cleanUp ? > > > I don't know yet. > Maybe there is some test, which breaking them when it runs? Or tests > are not run on those images? > I was thinking exactly the same. But no, this image has not run the tests. There are other images specially to download from hudson that are those after running tests :( -- Mariano http://marianopeck.wordpress.com

May 10, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Igor Stasenko

On 10 May 2011 11:27, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Tue, May 10, 2011 at 10:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 10 May 2011 09:48, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> > >> > >> > On Tue, May 10, 2011 at 9:41 AM, Marcus Denker <marcus.denker(a)inria.fr> >> > wrote: >> >> >> >> On May 10, 2011, at 9:32 AM, Mariano Martinez Peck wrote: >> >> >> >> > >> >> > what is even worst, is that even after removing those correct CM, and >> >> > doing a GC etc...they still don't disappear. >> >> > >> >> >> >> There is >> >> >> >> Â Â Â Â ScriptLoader new cleanUpMethods >> >> >> >> This is called from #cleanUpForRelease and normally should make sure >> >> there >> >> are no old methods. >> >> >> > >> > >> > hehehehe if I do: ScriptLoader new cleanUpForRelease, then inspect >> > ((CompiledMethod allInstances select:Â [:each | each trailer kind = >> > #VarLengthSourcePointer] ) ) >> > >> > they are not GC'ed and if then I click on the first element in the >> > inspector.... VM CRASH!!!Â with both, InterpreterVM and CogVM. >> > >> > :( >> > >> >> okay. it seems i found the offender. Its a CompiledMethod class>>cleanUp. >> It changing a source pointer of all non-installed methods to 0. > > Good catch!!!Â :)Â Â Anyway, why CompiledMethod class >>cleanUp would like to > destroy source pointers??? > If I understood correctly (please correct me), all compiled methods will > loose the pointer to sources and hence they will be decompiled after when > they are ask their source! Yes, if you wipe the sourcePointer, there is no way how you can get a source code of method. > > I must be wrong, because the dev image when it is build, it calls all > cleanUp methods for classes, so CompiledMethod class >> cleanUp shuld have > been called, but if I take the Pharo1.3 result, I can see the source code > (not decompiled) > But you can't see the source of those methods in browser, because browser works only with installed methods while cleanup touching only non-installed ones. >> >> When i do this, my image hangs. > > I have just tried and it crash!!!Â Actually, I evaluated CompiledMethod > cleanUp. And just after cmd+b in CompiledMethod (to browse it) -> crash > How it is possilbe it didn't crash while building the dev image?Â Â or the > first time I browse a class? > maybe this incorrect CM are created by the build process just after the > cleanUp ? > I don't know yet. Maybe there is some test, which breaking them when it runs? Or tests are not run on those images? > >> >> Now i thinking that it should actually use empty trailer for those >> methods i.e. CompiledMethodTrailer empty.. >> >> Still i found it strange why some methods has broken bytecode. > > Yes!! and why they are not GCed!! > >> >> My theory is that some nasty code somewhere copied a compiled methods >> using some unsafe technique, like: >> >> 1 to: oldMethod size do: [ :i | newMethod at: i put: (oldMethod at: i) ] > > I will search to see if I find something. > The thing is that it is reproducible. Each new dev image build from scratch > in a core, has these guys. > >> >> Because when you constructing compiled method normally (by compiling >> them) , there is no way how you can get broken compiled methods. (we >> would discover it much much earlier, > > yes, exactly. > >> >> and in fact CompiledMethodTrailers are working for more than a year in >> both pharo and squeak, and there was no any issues like this from >> their side). >> > > +1 > >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Best regards, Igor Stasenko AKA sig.

May 10, 2011

[Pharo-project] Time to rename copyWithTrailerBytes: ?

by Mariano Martinez Peck

If I understand correctly, before the trailers we used to use just an array of bytes...now we use a CompiledMethodTrailer. So, the method copyWithTrailerBytes: is misleading. cheers -- Mariano http://marianopeck.wordpress.com

May 10, 2011

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

by Mariano Martinez Peck

On Tue, May 10, 2011 at 11:40 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi. I cannot understand why you can use the MonticelloBrowser but not > Gofer. Are you behind a proxy? if true, check in the menu -> settings -> > Network -> Use HTTP proxy and "Proxy authentification". > > The packages to load SqueakDBX IN ORDER are: > > From repo http://source.squeakfoundation.org/FFI > > load : FFI-Pools-eem.2 > load : FFI-Kernel-tbn.20 > load : FFI-Tests-jcg.4 > load : FFI-MacOS-spd.5 > load : FFI-Unix-tbn.3 > load : FFI-Win32-ar.3 > > From repo http://www.squeaksource.com/SqueakDBX > > load : SqueakDBX-Smalltalk-Dialect-tbn.6 > load : SqueakDBX-Dialect-Squeak-MarianoMartinezPeck.6 > load : OpenDBX-Core-GuillermoPolito.283 > > > I don't want to dissapoint you, but be aware that for SqueakDBX you need > the library OpenDBX plus the native database libraries. This is explained in > http://www.squeakdbx.org/Architecture%20and%20desing > > In addition, this should be of help: > > http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX > http://www.squeakdbx.org/Compiling%20for%20different%20backends > > Finally, notice that when you have an error like the one of Gofer, you can > send by email PharoDebug.log which should have been created in the same > directory where your .image is. Such file contains all the stacktrace. > > Cheers > > Mariano > > > On Tue, May 10, 2011 at 8:27 AM, sourav roy <sourav_pharo(a)in.com> wrote: > >> >> Hi Peck, >> >> Instead of running the Gofer script, can I download the each package and >> load it in my Pharo. This I am asking because the office environment is >> secured because of which am not able to do load the required configuration >> packages via script. Please if it is possible for you the suggest me the >> names of the packages required to load SqueakDBX. >> >> P.S:Screen shot of the error given below. >> >> Thanks&Regards, >> >> [image: gogreen] >> >> *Sourav Roy|Misys Loan IQ Dev Team|HCL >> Technologies|SEZ-Bangalore|Mob:8861133201* >> >> *From:* Mariano Martinez Peck [mailto:marianopeck@gmail.com] >> *Sent:* Monday, May 09, 2011 6:06 PM >> *To:* Sourav Roy >> *Subject:* Re: Re: [Pharo-project] Issue in loading SqueakDBX Patch >> >> 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 >> >> *Error! Filename not specified.* >> >> *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 >> >> >> 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 > > -- Mariano http://marianopeck.wordpress.com

May 10, 2011

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

by Mariano Martinez Peck

Hi. I cannot understand why you can use the MonticelloBrowser but not Gofer. Are you behind a proxy? if true, check in the menu -> settings -> Network -> Use HTTP proxy and "Proxy authentification". The packages to load SqueakDBX IN ORDER are: >From repo http://source.squeakfoundation.org/FFI load : FFI-Pools-eem.2 load : FFI-Kernel-tbn.20 load : FFI-Tests-jcg.4 load : FFI-MacOS-spd.5 load : FFI-Unix-tbn.3 load : FFI-Win32-ar.3 >From repo http://www.squeaksource.com/SqueakDBX load : SqueakDBX-Smalltalk-Dialect-tbn.6 load : SqueakDBX-Dialect-Squeak-MarianoMartinezPeck.6 load : OpenDBX-Core-GuillermoPolito.283 I don't want to dissapoint you, but be aware that for SqueakDBX you need the library OpenDBX plus the native database libraries. This is explained in http://www.squeakdbx.org/Architecture%20and%20desing In addition, this should be of help: http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX http://www.squeakdbx.org/Compiling%20for%20different%20backends Finally, notice that when you have an error like the one of Gofer, you can send by email PharoDebug.log which should have been created in the same directory where your .image is. Such file contains all the stacktrace. Cheers Mariano On Tue, May 10, 2011 at 8:27 AM, sourav roy <sourav_pharo(a)in.com> wrote: > > Hi Peck, > > Instead of running the Gofer script, can I download the each package and > load it in my Pharo. This I am asking because the office environment is > secured because of which am not able to do load the required configuration > packages via script. Please if it is possible for you the suggest me the > names of the packages required to load SqueakDBX. > > P.S:Screen shot of the error given below. > > Thanks&Regards, > > [image: gogreen] > > *Sourav Roy|Misys Loan IQ Dev Team|HCL > Technologies|SEZ-Bangalore|Mob:8861133201* > > *From:* Mariano Martinez Peck [mailto:marianopeck@gmail.com] > *Sent:* Monday, May 09, 2011 6:06 PM > *To:* Sourav Roy > *Subject:* Re: Re: [Pharo-project] Issue in loading SqueakDBX Patch > > 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 > > *Error! Filename not specified.* > > *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 > > > 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 10, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

On Tue, May 10, 2011 at 10:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 10 May 2011 09:48, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > > > On Tue, May 10, 2011 at 9:41 AM, Marcus Denker <marcus.denker(a)inria.fr> > > wrote: > >> > >> On May 10, 2011, at 9:32 AM, Mariano Martinez Peck wrote: > >> > >> > > >> > what is even worst, is that even after removing those correct CM, and > >> > doing a GC etc...they still don't disappear. > >> > > >> > >> There is > >> > >> ScriptLoader new cleanUpMethods > >> > >> This is called from #cleanUpForRelease and normally should make sure > there > >> are no old methods. > >> > > > > > > hehehehe if I do: ScriptLoader new cleanUpForRelease, then inspect > > ((CompiledMethod allInstances select: [:each | each trailer kind = > > #VarLengthSourcePointer] ) ) > > > > they are not GC'ed and if then I click on the first element in the > > inspector.... VM CRASH!!! with both, InterpreterVM and CogVM. > > > > :( > > > > okay. it seems i found the offender. Its a CompiledMethod class>>cleanUp. > It changing a source pointer of all non-installed methods to 0. > Good catch!!! :) Anyway, why CompiledMethod class >>cleanUp would like to destroy source pointers??? If I understood correctly (please correct me), all compiled methods will loose the pointer to sources and hence they will be decompiled after when they are ask their source! I must be wrong, because the dev image when it is build, it calls all cleanUp methods for classes, so CompiledMethod class >> cleanUp shuld have been called, but if I take the Pharo1.3 result, I can see the source code (not decompiled) > > When i do this, my image hangs. > I have just tried and it crash!!! Actually, I evaluated CompiledMethod cleanUp. And just after cmd+b in CompiledMethod (to browse it) -> crash How it is possilbe it didn't crash while building the dev image? or the first time I browse a class? maybe this incorrect CM are created by the build process just after the cleanUp ? > Now i thinking that it should actually use empty trailer for those > methods i.e. CompiledMethodTrailer empty.. > Still i found it strange why some methods has broken bytecode. > Yes!! and why they are not GCed!! > > My theory is that some nasty code somewhere copied a compiled methods > using some unsafe technique, like: > > 1 to: oldMethod size do: [ :i | newMethod at: i put: (oldMethod at: i) ] > I will search to see if I find something. The thing is that it is reproducible. Each new dev image build from scratch in a core, has these guys. > > Because when you constructing compiled method normally (by compiling > them) , there is no way how you can get broken compiled methods. (we > would discover it much much earlier, > yes, exactly. > and in fact CompiledMethodTrailers are working for more than a year in > both pharo and squeak, and there was no any issues like this from > their side). > > +1 > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com

May 10, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Igor Stasenko

On 10 May 2011 09:48, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Tue, May 10, 2011 at 9:41 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: >> >> On May 10, 2011, at 9:32 AM, Mariano Martinez Peck wrote: >> >> > >> > what is even worst, is that even after removing those correct CM, and >> > doing a GC etc...they still don't disappear. >> > >> >> There is >> >> Â Â Â Â ScriptLoader new cleanUpMethods >> >> This is called from #cleanUpForRelease and normally should make sure there >> are no old methods. >> > > > hehehehe if I do: ScriptLoader new cleanUpForRelease, then inspect > ((CompiledMethod allInstances select:Â [:each | each trailer kind = > #VarLengthSourcePointer] ) ) > > they are not GC'ed and if then I click on the first element in the > inspector.... VM CRASH!!!Â with both, InterpreterVM and CogVM. > > :( > okay. it seems i found the offender. Its a CompiledMethod class>>cleanUp. It changing a source pointer of all non-installed methods to 0. When i do this, my image hangs. Now i thinking that it should actually use empty trailer for those methods i.e. CompiledMethodTrailer empty.. Still i found it strange why some methods has broken bytecode. My theory is that some nasty code somewhere copied a compiled methods using some unsafe technique, like: 1 to: oldMethod size do: [ :i | newMethod at: i put: (oldMethod at: i) ] Because when you constructing compiled method normally (by compiling them) , there is no way how you can get broken compiled methods. (we would discover it much much earlier, and in fact CompiledMethodTrailers are working for more than a year in both pharo and squeak, and there was no any issues like this from their side). -- Best regards, Igor Stasenko AKA sig.

May 10, 2011

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

by Benjamin

Exact, I haven't notice :) Thanks Ben On May 10, 2011, at 10:44 AM, Damien Cassou wrote: > On Tue, May 10, 2011 at 10:34 AM, Benjamin > <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> Here a screenshot of the second UI, more classic: > > Third and Fourth panes have the same name > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

May 10, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by Mariano Martinez Peck

> > So I would like to still know: > > 1) while those fucking CMs are not GCed > > 2) how they can be generated. > > > > I have spent the whole day and I couldn't :( I am more interested in > 1) > > Notice that I didn't do anything weird. I just took the default Pharo1.3 > > image. > > > you could take any method and just do > #copyWithTrailerBytes: > with any trailer you would like to test. > > Thanks. I don't understand how I can create a trailer with tempNames. Actually, I don't understand what string to pass as tempNames. In your #testEmbeddingTempNames you do: code := 'testEmbeddingSourceCode | trailer newTrailer code | trailer := CompiledMethodTrailer new. trailer sourceCode: code. newTrailer := trailer testEncoding. self assert: (newTrailer sourceCode = code).'. trailer tempNames: code. But I am not sure if that's correct. What does it means? that as temp names I send the full source code? I tried and doesn't work. And then, I read the following method which says something about writing the tempNames with a particular way: schematicTempNamesString "Answer the temp names for the current method node in a form that captures temp structure. The temps at each method and block scope level occur space-separated, with any indirect temps enclosed in parentheses. Each block level is enclosed in square brackets. e.g. 'method level temps (indirect temp)[block args and temps (indirect)]' This representation can be reconstituted into a blockExtentsToTempsMap by a CompiledMethod that has been copied with the schematicTempNamesString." You can also look at CompiledMethodTrailerTest for examples (see > #testEncoding). > > As for finding pointers.. have you tried to use pointer finder? :) > (it means i can't help with it more than you already know). > Yeah, I tried it. But maybe I am not seeing something :( If you want to try it by yourself, just take any Pharo1.3 image like: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/128/artif… And explore any of the pointers of ((CompiledMethod allInstances select: [:each | each trailer kind = #VarLengthSourcePointer] ) ) thanks for the effort Mariano > > > > Thanks Igor for your help. > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com

May 10, 2011