October 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] detect if image was saved with Cog

by Henrik Sperre Johansen

On 01.10.2012 13:30, Levente Uzonyi wrote: > On Mon, 1 Oct 2012, Max Leske wrote: > >> Hi guys >> >> Is there a way to find out (from outside of the image), if an image >> has been saved with Cog? What I would like to do is something like this: >> >> $ head -20 myImage.image | grep <some expression> >> >> The use case for this is seaside hosting, where we only have squeak >> VMs to run images, so when an image is uploaded that was saved with >> Cog that image cause trouble. >> Any ideas? > > Currently there are 3 image formats around 6502 (old interpreter > format, no closures), 6504 (new interpreter format with closures), > 6505 (Cog format). The first two bytes of the image file contain the > image format in little-endian (IIRC) format. Endianness in header depends on the platform the image was saved on. Which for all practical purposes, means little-endian these days. There is no symmetry in the format which allows you to bit-test endianness in a platform independent manner, afaik, the only "rule" is that format numbers which read as an existing format in the opposite endianness is disallowed. Cheers, Henry

Oct. 1, 2012

Re: [Pharo-project] detect if image was saved with Cog

by Sven Van Caekenberghe

On 01 Oct 2012, at 13:30, Levente Uzonyi <leves(a)elte.hu> wrote: > Currently there are 3 image formats around 6502 (old interpreter format, no closures), 6504 (new interpreter format with closures), 6505 (Cog format). The first two bytes of the image file contain the image format in little-endian (IIRC) format. So you can decide it by checking the first byte (head -c 1). If you only support the old interpreter format, then the following bash expression should work: > > [ $(head -c 1 $IMAGE_NAME) == 'f' ] SmalltalkImage current imagePath asFileReference readStreamDo: [ :stream | stream binary. (stream next: 2) reversed asInteger ]. to express your description in Smalltalk code then. Thanks for the explanation. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Oct. 1, 2012

Re: [Pharo-project] detect if image was saved with Cog

by David T. Lewis

On Mon, Oct 01, 2012 at 11:09:51AM +0200, Max Leske wrote: > Hi guys > > Is there a way to find out (from outside of the image), if an image has > been saved with Cog? What I would like to do is something like this: > > $ head -20 myImage.image | grep <some expression> > > The use case for this is seaside hosting, where we only have squeak VMs > to run images, so when an image is uploaded that was saved with Cog that > image cause trouble. > Any ideas? > > Cheers, > Max You should definitely update those older VMs if you can (http://squeakvm.org) but if that is not possible, here is how to check the image format from a shell script. 1) Load package ImageFormat from the VMMaker repository at http://source.squeak.org/VMMaker. 2) Evaluate "ImageFormat createCkStatusProgram" to generate source code ckformat.c. 3) Compile ckformat ($ cc -o ckformat ckformat.c). The ckformat program reads an image file header and prints the image format number on standard output. Non-zero exit status means the format could not be read (e.g. if it was not an image file). You can see how it is used in the /usr/local/bin/squeak script in the latest unix interpreter VMs from squeakvm.org. In your script you can do something like this: imagenumber=`ckformat myimage.image` if test $? -eq 0 then echo the image number is $imagenumber else echo could not read the image number fi If you are interested in the meanings of the various image format numbers, browse class ImageFormat. Dave

Oct. 1, 2012

Re: [Pharo-project] detect if image was saved with Cog

by Levente Uzonyi

On Mon, 1 Oct 2012, Max Leske wrote: > Hi guys > > Is there a way to find out (from outside of the image), if an image has been saved with Cog? What I would like to do is something like this: > > $ head -20 myImage.image | grep <some expression> > > The use case for this is seaside hosting, where we only have squeak VMs to run images, so when an image is uploaded that was saved with Cog that image cause trouble. > Any ideas? Currently there are 3 image formats around 6502 (old interpreter format, no closures), 6504 (new interpreter format with closures), 6505 (Cog format). The first two bytes of the image file contain the image format in little-endian (IIRC) format. So you can decide it by checking the first byte (head -c 1). If you only support the old interpreter format, then the following bash expression should work: [ $(head -c 1 $IMAGE_NAME) == 'f' ] Levente > > Cheers, > Max >

Oct. 1, 2012

Re: [Pharo-project] Problem with merging, changes and MC

by Camillo Bruni

On 2012-10-01, at 12:40, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Oct 1, 2012, at 11:19 AM, Mariano Martinez Peck wrote: > >> Hi. Together with Guille we found a problem and we were able to reproduce it. The thing is this... I have my FuelTest package with version MarcusDenker.286. Then I did a merge with the last version from Fuel repo (Name: FuelTests-MarianoMartinezPeck.289). Now, if you see the package in the MC browser, it looks like: >> >> * FuelTests (MarcusDenker.286, MarianoMartinezPeck.289) >> >> So now when I search for "changes" the #closestAncestorSnapshotIn: is wrong because it is NOT taking the last version. From what we could understand, the problem is that #closestAncestorVersionFor:ifNone: sends #breadthFirstAncestorsDo: and this last methods does not SORT the versions. So...since the .286 is first and .289 is last, it answers the wrong value. >> Just as a test, we did a "ancestors := ancestors reversed" in #breadthFirstAncestorsDo: and the "changes" work as expected. >> >> So...what should we do? change the #breadthFirstAncestorsDo: so that it does not depend on the "sort", fix the Ëmerge" so that it sorts the versions? something else? > > I have the impression that making sure that breadthFirstAncestors start from the latest makes sense. indeed sounds reasonable... what I always do with all the MC stuff I have no clue about, I just set up an with the changes and use it for some while :) if it works and all the MC tests pass, OK to go :P

Oct. 1, 2012

Re: [Pharo-project] detect if image was saved with Cog

by Sven Van Caekenberghe

I believe they have a custom VM with restricted primitives, Still, his question is relevant: how to interpret the image header ? I know there is a header with useful things like the initial extent. On 01 Oct 2012, at 12:15, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 1 October 2012 11:09, Max Leske <maxleske(a)gmail.com> wrote: >> Hi guys >> >> Is there a way to find out (from outside of the image), if an image has been saved with Cog? What I would like to do is something like this: >> >> $ head -20 myImage.image | grep <some expression> >> >> The use case for this is seaside hosting, where we only have squeak VMs to run images, so when an image is uploaded that was saved with Cog that image cause trouble. >> Any ideas? >> >> Cheers, >> Max > > get new queak vms, they now should support new image fromat used by cog > > -- > Best regards, > Igor Stasenko. >

Oct. 1, 2012

Re: [Pharo-project] Problem with merging, changes and MC

by StÃ©phane Ducasse

On Oct 1, 2012, at 11:19 AM, Mariano Martinez Peck wrote: > Hi. Together with Guille we found a problem and we were able to reproduce it. The thing is this... I have my FuelTest package with version MarcusDenker.286. Then I did a merge with the last version from Fuel repo (Name: FuelTests-MarianoMartinezPeck.289). Now, if you see the package in the MC browser, it looks like: > > * FuelTests (MarcusDenker.286, MarianoMartinezPeck.289) > > So now when I search for "changes" the #closestAncestorSnapshotIn: is wrong because it is NOT taking the last version. From what we could understand, the problem is that #closestAncestorVersionFor:ifNone: sends #breadthFirstAncestorsDo: and this last methods does not SORT the versions. So...since the .286 is first and .289 is last, it answers the wrong value. > Just as a test, we did a "ancestors := ancestors reversed" in #breadthFirstAncestorsDo: and the "changes" work as expected. > > So...what should we do? change the #breadthFirstAncestorsDo: so that it does not depend on the "sort", fix the Ëmerge" so that it sorts the versions? something else? I have the impression that making sure that breadthFirstAncestors start from the latest makes sense. Stef

Oct. 1, 2012

Re: [Pharo-project] detect if image was saved with Cog

by Igor Stasenko

On 1 October 2012 11:09, Max Leske <maxleske(a)gmail.com> wrote: > Hi guys > > Is there a way to find out (from outside of the image), if an image has been saved with Cog? What I would like to do is something like this: > > $ head -20 myImage.image | grep <some expression> > > The use case for this is seaside hosting, where we only have squeak VMs to run images, so when an image is uploaded that was saved with Cog that image cause trouble. > Any ideas? > > Cheers, > Max get new queak vms, they now should support new image fromat used by cog -- Best regards, Igor Stasenko.

Oct. 1, 2012

[Pharo-project] Problem with merging, changes and MC

by Mariano Martinez Peck

Hi. Together with Guille we found a problem and we were able to reproduce it. The thing is this... I have my FuelTest package with version MarcusDenker.286. Then I did a merge with the last version from Fuel repo (Name: FuelTests-MarianoMartinezPeck.289). Now, if you see the package in the MC browser, it looks like: * FuelTests (MarcusDenker.286, MarianoMartinezPeck.289) So now when I search for "changes" the #closestAncestorSnapshotIn: is wrong because it is NOT taking the last version. From what we could understand, the problem is that #closestAncestorVersionFor:ifNone: sends #breadthFirstAncestorsDo: and this last methods does not SORT the versions. So...since the .286 is first and .289 is last, it answers the wrong value. Just as a test, we did a "ancestors := ancestors reversed" in #breadthFirstAncestorsDo: and the "changes" work as expected. So...what should we do? change the #breadthFirstAncestorsDo: so that it does not depend on the "sort", fix the Ëmerge" so that it sorts the versions? something else? Thanks! -- Mariano http://marianopeck.wordpress.com

Oct. 1, 2012

[Pharo-project] detect if image was saved with Cog

by Max Leske

Hi guys Is there a way to find out (from outside of the image), if an image has been saved with Cog? What I would like to do is something like this: $ head -20 myImage.image | grep <some expression> The use case for this is seaside hosting, where we only have squeak VMs to run images, so when an image is uploaded that was saved with Cog that image cause trouble. Any ideas? Cheers, Max

Oct. 1, 2012