- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Stan Krupoderov

Hi Esteban, > we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version Thanks for clarification. I see your point. Will it be always the same way or it should be changed once VM and Pharo 6 are stabilized? How update scenario should be handled in this case on the user side? Will it be File-out and File-in for all user changes? And unfortunately this doesn't add clarity on why Pharo 5 is so unstable out of the box and if there any plans to fix existing issues in Pharo 5. Do you have any thoughts on this matter? Can we help with this? On Wed, Mar 29, 2017 at 1:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: > >> wellâ¦ > >> > >> Latest VM is intended to work with latest Pharo, not with older > versions. > >> Latest VM is *always* an experimental/unstable VM that needs to be > consideredâ¦ that, experimental and unstable. Otherwise there would not be > point on having the distinction between stable/latest, isnât? > >> > > > >> So, no, Latest VM (which can also be known as âalpha vmâ) has not > broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 > Alphaâ). > >> > >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo > 5â. > >> > >> Of course, you can live at the edge, but that doesnât means something > is broken when something fails if premises are not fulfilled :) > > > > Well considering VM for Pharo 5 never worked for me properly, whether it > was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a > choice but to use the latest. If there is a better way then I am all ears, > constantly dealing with crashing VM when I need to get work done is > extremely frustrating... > > > > Also I was under the impression that newer VM should work with older > images, with the only exception being Cog/Spur change. Or should I have six > different VMs and Pharo Launcher with six different VM configurations? > > we moved the paradigm a couple of years ago: each Pharo version comes with > his own VM version (Other smalltalks do that too). > Being infinite backward compatible is a lot of pain :) > > so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement for > PharoLauncher: you ship with latest stable but you can always download > newers or olders (this is not yet implemented, is just a requirement I > addedâ¦ well, couple of years ago when we changed the way we wanted VMs to > work). > > Esteban > > > > > Peter > > > >> > >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may > happen, since this is all alfa :P) > >> > >> I donât know if âworkarounding the VMâ (by renaming libfreetype) will > work, but if that works, ONCE we move latest vm to stable status we can > consider backporting it to Pharo 5. > >> > >> Esteban > >> > >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >>> > >>> The new "fixed" compactor VM has broken FT... > >>> > >>> So any text drawn on Athens canvas results in red cross... > >>> > >>> Error in... > >>> > >>> CairoFontFace class>>primFtFace:loadFlags: > >>> > >>> 'Unable to find function address' > >>> > >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > >>> > >>> (Windows VM latest, Pharo 5) > >>> > >> > >> > > > > > -- Regards, Stanislav S. Krupoderov

March 29, 2017

Path>>/ and ..

by Alistair Grant

Hi All, The current implementation of Path>>/, while functional, seems to me to create poorly formed paths, e.g.: ('/a/b/c/d' asFileReference / '../e') path ==> "Path / 'a' / 'b' / 'c' / 'd' / '../e'" As can be seen above, the last segment is '../e'. I would expect the result to be: "Path / 'a' / 'b' / 'c' / 'e'" Is there a reason for the current behaviour? If not, are people open to modifying Path>>/ to produce the suggested result above (in Pharo 7)? The method below produces the modified result above and doesn't change the result of running all automated tests. If this is going to be added to Pharo 7 I'll create an additional automated test to check that it is working properly. Cheers, Alistair 'From Pharo6.0 of 13 May 2016 [Latest update: #60451] on 29 March 2017 at 9:40:41.681228 am'! !Path methodsFor: 'navigating' stamp: 'AlistairGrant 3/29/2017 09:39'! / aString | path | aString isEmptyOrNil ifTrue: [ Error signal: 'Path element cannot be empty or nil']. ^self resolve: (Path from: aString) ! !

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Esteban Lorenzano

> On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: >> wellâ¦ >> >> Latest VM is intended to work with latest Pharo, not with older versions. >> Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? >> > >> So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). >> >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. >> >> Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) > > Well considering VM for Pharo 5 never worked for me properly, whether it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a choice but to use the latest. If there is a better way then I am all ears, constantly dealing with crashing VM when I need to get work done is extremely frustrating... > > Also I was under the impression that newer VM should work with older images, with the only exception being Cog/Spur change. Or should I have six different VMs and Pharo Launcher with six different VM configurations? we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version (Other smalltalks do that too). Being infinite backward compatible is a lot of pain :) so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement for PharoLauncher: you ship with latest stable but you can always download newers or olders (this is not yet implemented, is just a requirement I addedâ¦ well, couple of years ago when we changed the way we wanted VMs to work). Esteban > > Peter > >> >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) >> >> I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. >> >> Esteban >> >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> >>> The new "fixed" compactor VM has broken FT... >>> >>> So any text drawn on Athens canvas results in red cross... >>> >>> Error in... >>> >>> CairoFontFace class>>primFtFace:loadFlags: >>> >>> 'Unable to find function address' >>> >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll >>> >>> (Windows VM latest, Pharo 5) >>> >> >> >

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Peter Uhnak

On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: > wellâ¦ > > Latest VM is intended to work with latest Pharo, not with older versions. > Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? > > So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). > > BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. > > Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) Well considering VM for Pharo 5 never worked for me properly, whether it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a choice but to use the latest. If there is a better way then I am all ears, constantly dealing with crashing VM when I need to get work done is extremely frustrating... Also I was under the impression that newer VM should work with older images, with the only exception being Cog/Spur change. Or should I have six different VMs and Pharo Launcher with six different VM configurations? Peter > > Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) > > I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. > > Esteban > > > On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > The new "fixed" compactor VM has broken FT... > > > > So any text drawn on Athens canvas results in red cross... > > > > Error in... > > > > CairoFontFace class>>primFtFace:loadFlags: > > > > 'Unable to find function address' > > > > Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > > > > (Windows VM latest, Pharo 5) > > > >

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Esteban Lorenzano

wellâ¦ Latest VM is intended to work with latest Pharo, not with older versions. Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. Esteban > On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > The new "fixed" compactor VM has broken FT... > > So any text drawn on Athens canvas results in red cross... > > Error in... > > CairoFontFace class>>primFtFace:loadFlags: > > 'Unable to find function address' > > Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > > (Windows VM latest, Pharo 5) >

March 29, 2017

Re: [Pharo-dev] debugger inspector pane different than inspect pane?

by Andrei Chis

Not aware of this bug. I tried to debug a few other objects that have custom tree presentations and they seem to work. I'll need a way to reproduce this. Can you paste the code of the custom presentation that is problematic. Cheers, Andrei On Wed, Mar 29, 2017 at 9:11 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi andrei > > I'm debugger a node of a tree and in the debugger > the tree pane is empty. Now when I click on the node and inspect > it I get a tree representation. > > I do not know if you are aware of this behavior. > > Stef >

March 29, 2017

the new "fixed" compactor VM has FT broken...

by Peter Uhnak

The new "fixed" compactor VM has broken FT... So any text drawn on Athens canvas results in red cross... Error in... CairoFontFace class>>primFtFace:loadFlags: 'Unable to find function address' Apparently because someone renamed libfreetype-6.dll to libfreetype.dll (Windows VM latest, Pharo 5)

March 29, 2017

Re: [Pharo-dev] How to install Iceberg?

by Christophe Demarey

Hi, > Le 25 mars 2017 Ã 14:04, Alistair Grant <akgrant0710(a)gmail.com> a Ã©crit : > > Hi Christophe, > > On 23 March 2017 at 21:54, Christophe Demarey > <christophe.demarey(a)inria.fr> wrote: >> Hi Alex, >> >> the master branch is quite old. >> Please use dev-0.4 branch with the latest stable VM. > > Can you remove the dev-0.4 branch once it has been merged back on to > master so we know that it should no longer be used? > > (There are quite a few branches in the repository, maybe some others > could be removed as well?) yes, it is a good idea to remove obsolete branches. I will discuss with Esteban because I have no rights on iceberg repo to do so.

March 29, 2017

Re: [Pharo-dev] Crashes on snapshot with the new compactor

by Stephane Ducasse

oki tx On Wed, Mar 29, 2017 at 8:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > latest :) > > On 29 Mar 2017, at 08:48, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > Esteban > > is there a new vm that we should use? > > Stef > > On Wed, Mar 29, 2017 at 8:01 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> we have our official distribution in our file server. >> pharo vmâs can be download here: >> >> http://files.pharo.org/get-files/60 >> there is also a bintray, but is only as mirror/backup: https://dl.bint >> ray.com/pharo-project/pharo-vm/ >> >> cheers, >> Esteban >> >> ps: I think Pharo is also on osvm bintray but with a weird name (not sure >> about that) :P >> >> >> On 28 Mar 2017, at 23:29, Stanislav Krupoderov <pashelper(a)gmail.com> >> wrote: >> >> Hi Eliot, >> >> The bintray files are here: >> https://bintray.com/opensmalltalk/vm/cog/201703272314 >> >> >> Where can I find pharo binary for x86/x64 linux? I don't see it on >> bintray. >> >> >> >> -- >> View this message in context: http://forum.world.st/Crashes- >> on-snapshot-with-the-new-compactor-tp4939961p4940268.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com <http://nabble.com/>. >> >> >> > >

March 29, 2017

debugger inspector pane different than inspect pane?

by Stephane Ducasse

Hi andrei I'm debugger a node of a tree and in the debugger the tree pane is empty. Now when I click on the node and inspect it I get a tree representation. I do not know if you are aware of this behavior. Stef

March 29, 2017