March 2013 - Pharo-users - lists.pharo.org

PlugComputer

by Paul Davidowitz

Does Pharo run on PlugComputer (http://www.plugcomputer.org/)?

March 3, 2013

Re: [Pharo-users] segmentation fault on startup with no stack printed.... any way to recover the image?

by stephane ducasse

On Mar 3, 2013, at 4:10 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > On 03/03/2013 06:57 AM, Paul DeBruicker wrote: >> If I use the broken image's changes file and a more recent image of mine >> rather than the base Pharo 1.4 image I get this notice: >> >> "this image has never been saved since changes were compressed" >> >> Not sure what to make of that. I thought I might be able to save some >> work by using an older version of the broken image from a backup of my >> laptop. > > > If I use the next older image of mine this message does not appear. The > image with that notice had had 'cleanUpForRelease' run in it prior to > the its most recent save. ok for the release we reset a lot of behavior. So probably saving it once can help.

March 3, 2013

Re: [Pharo-users] segmentation fault on startup with no stack printed.... any way to recover the image?

by stephane ducasse

On Mar 3, 2013, at 3:57 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi Stef, > > If I use a base Pharo-1.4 image I can recover the changes so thanks for > pointing that out. ok even better. > Is there a way to skip over the doIts that I > might've done in an 'explore' window during the 'recover changes' process? Normally you can mark (filter) the entries (now pay attention since class def are doit (not good) but we hope that the new change model will help us addressing this change. > > > > If I use the broken image's changes file and a more recent image of mine > rather than the base Pharo 1.4 image I get this notice: > > "this image has never been saved since changes were compressed" Ok may be my approach was not that good :). In VW we could receover from another change file and we should add that behavior to Pharo too. > Not sure what to make of that. I thought I might be able to save some > work by using an older version of the broken image from a backup of my > laptop. > > > I don't have a debugging VM but this is what gdb outputs for the crash: > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000000419835 in initializeInterpreter () strange. It should not crash. Now eliot fixed several bugs related to become: and they were bringing a lot of instability to the system. I hope that we will get to a stable point soon. Stef > > > Thanks again > > Paul > > > On 03/03/2013 06:43 AM, stephane ducasse wrote: >> Hi paul >> >> did you try to receover the changes? >> we should improve this part too >> did you try the following: >> - take a fresh 1.4 >> - rename your change file as the change of the new version >> - and do recover ? >> >> Stef >> On Mar 3, 2013, at 3:36 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> >>> My laptop battery ran down when I was not paying attention. I saved the >>> image at about 6PM last night. The modification date on the image and >>> changes file is 3:15AM. I'm guessing that is when the battery died. >>> When I attempt to start the image (with cog or the interpreter vm) I get >>> >>> Segmentation fault (core dumped) >>> >>> >>> It does not print anything to the PharoDebug.log. Is there a process to >>> follow to attempt to recover the image? If I drag the changes file onto >>> another clean Pharo 1.4 image, I'm not able to go back as far as I'd >>> like. Ideally I would be able to get all the changes between the base >>> Pharo 1.4 image and the image I lost. >>> >>> >>> Thanks for any guidance you can provide >>> >> >> > >

March 3, 2013

Re: [Pharo-users] segmentation fault on startup with no stack printed.... any way to recover the image?

by Paul DeBruicker

On 03/03/2013 06:57 AM, Paul DeBruicker wrote: > If I use the broken image's changes file and a more recent image of mine > rather than the base Pharo 1.4 image I get this notice: > > "this image has never been saved since changes were compressed" > > Not sure what to make of that. I thought I might be able to save some > work by using an older version of the broken image from a backup of my > laptop. If I use the next older image of mine this message does not appear. The image with that notice had had 'cleanUpForRelease' run in it prior to the its most recent save.

March 3, 2013

Re: [Pharo-users] segmentation fault on startup with no stack printed.... any way to recover the image?

by Paul DeBruicker

Hi Stef, If I use a base Pharo-1.4 image I can recover the changes so thanks for pointing that out. Is there a way to skip over the doIts that I might've done in an 'explore' window during the 'recover changes' process? If I use the broken image's changes file and a more recent image of mine rather than the base Pharo 1.4 image I get this notice: "this image has never been saved since changes were compressed" Not sure what to make of that. I thought I might be able to save some work by using an older version of the broken image from a backup of my laptop. I don't have a debugging VM but this is what gdb outputs for the crash: Program received signal SIGSEGV, Segmentation fault. 0x0000000000419835 in initializeInterpreter () Thanks again Paul On 03/03/2013 06:43 AM, stephane ducasse wrote: > Hi paul > > did you try to receover the changes? > we should improve this part too > did you try the following: > - take a fresh 1.4 > - rename your change file as the change of the new version > - and do recover ? > > Stef > On Mar 3, 2013, at 3:36 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> My laptop battery ran down when I was not paying attention. I saved the >> image at about 6PM last night. The modification date on the image and >> changes file is 3:15AM. I'm guessing that is when the battery died. >> When I attempt to start the image (with cog or the interpreter vm) I get >> >> Segmentation fault (core dumped) >> >> >> It does not print anything to the PharoDebug.log. Is there a process to >> follow to attempt to recover the image? If I drag the changes file onto >> another clean Pharo 1.4 image, I'm not able to go back as far as I'd >> like. Ideally I would be able to get all the changes between the base >> Pharo 1.4 image and the image I lost. >> >> >> Thanks for any guidance you can provide >> > >

March 3, 2013

Re: [Pharo-users] segmentation fault on startup with no stack printed.... any way to recover the image?

by stephane ducasse

Hi paul did you try to receover the changes? we should improve this part too did you try the following: - take a fresh 1.4 - rename your change file as the change of the new version - and do recover ? Stef On Mar 3, 2013, at 3:36 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > My laptop battery ran down when I was not paying attention. I saved the > image at about 6PM last night. The modification date on the image and > changes file is 3:15AM. I'm guessing that is when the battery died. > When I attempt to start the image (with cog or the interpreter vm) I get > > Segmentation fault (core dumped) > > > It does not print anything to the PharoDebug.log. Is there a process to > follow to attempt to recover the image? If I drag the changes file onto > another clean Pharo 1.4 image, I'm not able to go back as far as I'd > like. Ideally I would be able to get all the changes between the base > Pharo 1.4 image and the image I lost. > > > Thanks for any guidance you can provide >

March 3, 2013

segmentation fault on startup with no stack printed.... any way to recover the image?

by Paul DeBruicker

My laptop battery ran down when I was not paying attention. I saved the image at about 6PM last night. The modification date on the image and changes file is 3:15AM. I'm guessing that is when the battery died. When I attempt to start the image (with cog or the interpreter vm) I get Segmentation fault (core dumped) It does not print anything to the PharoDebug.log. Is there a process to follow to attempt to recover the image? If I drag the changes file onto another clean Pharo 1.4 image, I'm not able to go back as far as I'd like. Ideally I would be able to get all the changes between the base Pharo 1.4 image and the image I lost. Thanks for any guidance you can provide

March 3, 2013

[ANN] Moose 4.7

by Tudor Girba

We are happy to announce the Moose Suite version 4.7: http://moosetechnology.org/download What is new: â¢ Integration of the Roassal visualization engine â¢ New PetitParser browser with integrated refactorings â¢ Improved Glamorous Toolkit for Pharo including the Glamorous Inspector and Debugger â¢ Several features in Glamour including Watcher support (similar to OS X preview) â¢ Significant improvements in FAMIX â¢ Improved external VerveineJ parser for Java â¢ Based on Pharo 1.4 A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Have fun, The Moose Team

March 3, 2013

Re: [Pharo-users] Release of the Pharo consortium web site

by phil＠highoctane.be

Cool. Now time to fill in some paperwork for membership then. I'll do that this WE. Phil 2013/3/1 Cameron Sanders <camsanders(a)aol.com>: > Very nice. Congratulations and Thanks! > -Cam > > On Fri, Mar 1, 2013 at 11:52 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Hi guys >> >> After some efforts, we are proud to announce the consortium around Pharo. >> >> http://consortium.pharo.org >> >> With such consortium, companies and academic partners will be able to >> collaborate and sustain the development of the Pharo environment and >> ecosystem. Today we announce the release of the beta version of the official >> consortium website. >> >> Invest in your future, participate to the consortium! >> >> Our goal is to be able to pay a couple of full-time engineers to build a >> bright future for everyone. >> >> Thanks >> Esteban for the effort, >> lusy for the design, and >> our first members: >> Inria, VMWare, yesplan, 2denker, madEnvironment, BetaNine, >> Versus for their trust >> >> We wish you a lot of business and success! >> >> The Pharo Team > >

March 1, 2013

Re: [Pharo-users] Release of the Pharo consortium web site

by Cameron Sanders

Very nice. Congratulations and Thanks! -Cam On Fri, Mar 1, 2013 at 11:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > After some efforts, we are proud to announce the consortium around Pharo. > > http://consortium.pharo.org > > With such consortium, companies and academic partners will be able to > collaborate and sustain the development of the Pharo environment and > ecosystem. Today we announce the release of the beta version of the > official consortium website. > > Invest in your future, participate to the consortium! > > Our goal is to be able to pay a couple of full-time engineers to build a > bright future for everyone. > > Thanks > Esteban for the effort, > lusy for the design, and > our first members: > Inria, VMWare, yesplan, 2denker, madEnvironment, BetaNine, > Versus for their trust > > We wish you a lot of business and success! > > The Pharo Team >

March 1, 2013