- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo Image Freeze

by Peter UhnÃ¡k

There is a shortcut "alt + . (dot)" (maybe ctrl/cmd depending on platform), that will break the current execution and show the debugger (which you can then close) - useful if you have infinite loops and so forth. Peter On Fri, Apr 17, 2015 at 1:51 AM, Gaurav Singh <grvanm.coder(a)gmail.com> wrote: > Is there any way to get back the Pharo image working when it freezes > without closing the Pharo image because many times the work isn't saved and > then it costs a lot restarting the pharo image? >

April 16, 2015

Pharo Image Freeze

by Gaurav Singh

Is there any way to get back the Pharo image working when it freezes without closing the Pharo image because many times the work isn't saved and then it costs a lot restarting the pharo image?

April 16, 2015

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3311/. These should fix the regression introduced by the map changes in 3308. They certainly fix the two crashes I've looked at, one an update of a squeak trunk image and the other the startup of recent Newspeak images. Apologies for the inconvenience. CogVM binaries as per VMMaker.oscog-eem.1204/r3311 Cogits: Fix regression in map machinery due to adding AnnotationExtension scheme. findMapLocationForMcpc:inMethod: must not be confused by IsDisplacementX2N bytes. This is likely the cause of the recent crashes with r3308 and earlier. Introduce marryFrameCopiesTemps and use it to not copy temps in Spur context creation trampolines. Change initial usage counts to keep more recently jitted methods around for longer, and do *not* throw away PICs in freeOlderMethodsForCompaction, so that there's a better chance of Sista finding send and branch data for the tripping method. extendedPushBytecode /does/ need a frame. Don't save the header in a scratch register unless it is useful to do so in the Spur at:[put:] primitives. Fix slip in genGetNumBytesOf:into:. And notice that genGetFormatOf:into:baseHeaderIntoScratch: et al can use byte access to get at format, as intended in the Spur header design. Fix unlinking dynamic super sends. Reduce false positives in access control violation reporting by marking the super send we actually use as privileged. Remove unused Newspeak bytecodes. Internal: Fix code generation bug surfaced by inline primitives. On x86 movb N(%reg),%rl can only store into al, bl, cl & dl, whereas movzbl can store into any reg. On ARM move byte also zero-extends. So change definition of MoveMbrR to always zero-extend, use movzbl on x86 and remove all the MoveCq: 0 R: used to zero the bits of the target of a MoveMb:r:R:. And now that we have genGetNumSlotsOf:into:, use it. Fix a slip in genTrinaryInlinePrimitive:, meet constraint that the target must be in ReceiverResultReg, and do a better job of register allocation there-in. Do dead code elimination for the branch following an inlined comparison (this is done in genBinaryInlineComparison:opFalse:destReg: copying the scheme in genSpecialSelectorEqualsEquals). Do register allocation in the right place in genUnaryInlinePrimitive:. Fix overflow slot access in genGetNumSlotsOf:into: et al. Fix several slips in inline primitive generation: Object>>at:put: needs to include a store check. Some register allocation code was wrong. Some results needed converting to SmallIntegers and recording results as pushed on the sim stack. Change callPrimitiveBytecode to genCallPrimitiveBytecode in the Cogit. remove the misnomer genConvertIntegerToSmallIntegerInScratchReg: Type of AbstractInstruction opcode must be unsigned now that we have more than 128 opcodes (XCHGRR pushed things over the top). Lay the groundwork for 32-bit intra-zone jumps and calls on ARM by introducing CallFull and JumpFull (and rewrites thereof) that are expected to span the full address space, leaving Call/JumpLong to span merely the 16mb code zone. On x86 CallFull and JumpFull simply default to Call/JumpLong. Replace bytecode trapIfNotInstanceOf by jumpIfNotInstanceOfOrPop. Rewrote the JIT logic for traps to be able to write trap trampolines calls at the end of the cogMethod. Refactor the slot store and store check machinery to take an inFrame: argument and hence deal with the store check in genInnerPrimitiveAtPut: on ARM. Fix limitation with MoveRXbrR; can only do movb from %al through %dl, so swap with %eax around movb. Fix mistake with genGetNumBytesOf:into: by refactoring genGetFormatOf:into:baseHeaderIntoScratch: into genGetBits:ofFormatByteOf:into:baseHeaderIntoScratch: and hence fetching and subtracting only odd bits of format. Correct the in-line primitive SmallInteger comparisons; CmpXR is confusing ;-) Fix var op var unsafe byte at:. Result must be converted to SmallInteger. Correct the generated Slang for the new register allocation code by adding a read-before-written pass to C generation that initializes variables read-before-written with 0 (the C equivalent of nil). fix a bug where sometimes register allocation was marking ReceiverResultReg as dead whereas it was still alive. Added some abstraction over register allocation. This is now used in inline primitives.

April 16, 2015

New User Question on Reddit

by Sean P. DeNigris

https://news.ycombinator.com/item?id=9390760 I installed this for Ubuntu 12.04. When I fired it up, it requested I choose and build a source file (different from Pharo 3). Then when it started, it said, "Pharo cannot locate the source file named /usr/lib/pharo-vm/PharoV40.sources. Any ideas what to do? TIA, Steve ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-User-Question-on-Reddit-tp4820098.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

GTSpotter and example previews

by Nicolai Hess

Why is this in the release? GTSpotter now shows the result of gtExamples in the preview. This looks so ugly. (for example browse the "Examples" cateogry for GLMCompositeBrick) If new features aren't mentioned anywhere, it is pretty difficult to test or to review them.

April 16, 2015

Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!

by phil＠highoctane.be

stef what about next tuesday? phil Le 16 avr. 2015 22:44, "stepharo" <stepharo(a)free.fr> a Ã©crit : > yes phil tell us. > > Stef > > Le 16/4/15 12:11, phil(a)highoctane.be a Ã©crit : > > > Le 16 avr. 2015 11:56, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > > > > Great job! > > > > Thank you everyone for the contributions, support and trust. > > One more out of the door. > That's great. > > Anyone interested in doing a podcast episode on this releasr? Chime in. > > Phil > > > > > Cheers, > > Doru > > > > > > On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >> > >> Please spread widely. > >> Sorry for multiple posts. > >> > >> (this post can be see here: http://pharo.org/news/pharo-4.0-released) > >> > >> Dear World, > >> > >> Pharo 4.0 (http://www.pharo.org) is here. > >> > >> Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > >> > >> Many things have changed in Pharo. Here are some highlights: > >> - Inspector/Playground/Spotter are new moldable development tools for > inspecting, coding and searching objects. > >> - Slots model instance variables as first class entities and enable > meta-programming on this level. > >> - ShoreLine reporter introduces a way to report system errors and > collect statistics, that we will use for future improvements > >> - Dark theme. > >> > >> These are just the more prominent highlights, but the details are just > as important. We have closed 1697 issues in Pharo 4. Take a moment to go > through a more detailed recount of the progress: > >> > >> > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > >> > >> Pharo is improving on many fronts, but one of the most prominent > changes is the addition of moldable tools for inspection and search. These > tools provide extension mechanisms that allow every object to define ways > in which it can be understood effectively. To provide an idea of the impact > of the already existing extensions, the map below shows the Pharo classes > grouped in packages, highlighting in red those parts of the system that > have at least one such custom view coming with the main distribution. The > spread of these extensions shows that moldability is powerful mechanism > that can be used in many contexts. > >> > >> > >> Remember that Pharo is your platform. We thank all the contributors of > this release: > >> > >> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe > Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, > Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei > Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, > Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane > Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, > Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, > Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, > Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max > Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot > Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, > Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, > Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian > Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, > Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin > >> > >> And all those who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > >> > >> Pharo 4.0 is another big step. And, the best is yet to come. > >> > >> Enjoy! > >> The Pharo Team > >> > >> > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > >

April 16, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by stepharo

Le 16/4/15 15:29, Sean P. DeNigris a Ã©crit : > laurent laffont wrote >> Note that the pkg files are hosted at https://github.com/lolgzs/pharo-aur/ > Should we fork this under the Pharo team? IMHO it is confusing to have our > build system scattered between various repos owned by different people. What > do you think? group things please. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-ArchLinux-pharo-vm-pharo-launcher-packages-tp4749… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 16, 2015

Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!

by stepharo

yes phil tell us. Stef Le 16/4/15 12:11, phil(a)highoctane.be a Ã©crit : > > > Le 16 avr. 2015 11:56, "Tudor Girba" <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> a Ã©crit : > > > > Great job! > > > > Thank you everyone for the contributions, support and trust. > > One more out of the door. > That's great. > > Anyone interested in doing a podcast episode on this releasr? Chime in. > > Phil > > > > > Cheers, > > Doru > > > > > > On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano > <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >> > >> > >> Please spread widely. > >> Sorry for multiple posts. > >> > >> (this post can be see here: http://pharo.org/news/pharo-4.0-released) > >> > >> Dear World, > >> > >> Pharo 4.0 (http://www.pharo.org) is here. > >> > >> Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > >> > >> Many things have changed in Pharo. Here are some highlights: > >> - Inspector/Playground/Spotter are new moldable development tools > for inspecting, coding and searching objects. > >> - Slots model instance variables as first class entities and enable > meta-programming on this level. > >> - ShoreLine reporter introduces a way to report system errors and > collect statistics, that we will use for future improvements > >> - Dark theme. > >> > >> These are just the more prominent highlights, but the details are > just as important. We have closed 1697 issues in Pharo 4. Take a > moment to go through a more detailed recount of the progress: > >> > >> > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > >> > >> Pharo is improving on many fronts, but one of the most prominent > changes is the addition of moldable tools for inspection and search. > These tools provide extension mechanisms that allow every object to > define ways in which it can be understood effectively. To provide an > idea of the impact of the already existing extensions, the map below > shows the Pharo classes grouped in packages, highlighting in red those > parts of the system that have at least one such custom view coming > with the main distribution. The spread of these extensions shows that > moldability is powerful mechanism that can be used in many contexts. > >> > >> > >> Remember that Pharo is your platform. We thank all the contributors > of this release: > >> > >> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe > Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent > Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven > Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, > Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso > Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus > Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc > Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, > Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale > Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, > Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, > David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, > Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan > Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik > Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, > Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres > Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin > Walk, Richard Wettel, Dmitri Zagidulin > >> > >> And all those who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > >> > >> Pharo 4.0 is another big step. And, the best is yet to come. > >> > >> Enjoy! > >> The Pharo Team > >> > >> > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" >

April 16, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Jean-Christophe Bach

* Damien Cassou <damien.cassou(a)inria.fr> [16.04.2015. @17:13:45 +0200]: > > Sean P. DeNigris <sean(a)clipperadams.com> writes: > > > Thanks for the clarification! Where are the Nix and Gentoo infrastructure > > hosted? I think we should collect all of these things under github/pharo > > for Nix, this is in the nixpkgs repository: > https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/pharo > > for Gentoo, it seems that several people contributed several recipes. I > put JC on CC so he can tell more. Pharo is not in the official Portage tree, but there is an overlay that includes a pharo ebuild: https://bitbucket.org/erosa/erosa-overlay Note that Gentoo ebuilds are more "recipes" than "packages". I wanted to write my own overlay with the real Gentoo style (i.e. with full compilation), but my latest attempt to compile the whole thing failed. I will probably write one for Pharo 4. JC

April 16, 2015

Versioning Jenkins Logic

by Sean P. DeNigris

Right now, the https://ci.inria.fr/pharo/view/4.0-VM/job/PharoVM-CentOs6 Jenkins job has the following shell script embedded in Jenkins. As you can see, there is quite a bit of logic there. Wouldn't it be better to put this type of thing under SCM? If so, I'm happy to do it, but where would be the best place? Is there an existing location that could fit? #!bash -lex cd "$WORKSPACE" # Set environment ============================================================ ZIP_FILTER='*' if [ "$OS" == "win" ]; then set -e # Stop the execution if a command fails! ZIP_FILTER=' *.exe *.dll' fi # Download the latest sources ================================================ wget --quiet files.pharo.org/vm/src/vmmaker-image.zip wget --quiet files.pharo.org/vm/src/cog.tar.gz # Unpack sources ============================================================= tar -xzf cog.tar.gz || echo # echo needed for Windows build (error on symlinks creation) mkdir -p cog/build mkdir -p cog/image cd cog/image unzip -o ../../vmmaker-image.zip # Generate sources =========================================================== #wget -O- get.pharo.org/vm40 | bash #wget -O pharovm-centos65.zip https://github.com/philippeback/pharovm-centos65/archive/master.zip #unzip pharovm-centos65.zip #mv pharovm-centos65-master/zeroconf-centos/* . #rmdir pharovm-centos65-master/zeroconf-centos # Only execute for a new slave # cd pharovm-centos65-master # sudo install-requisites.sh wget -O vm.zip http://files.pharo.org/vm/pharo/linux/centos/latest.zip unzip vm.zip wget http://files.pharo.org/sources/PharoV30.sources.zip unzip PharoV30.sources.zip ./pharo --nodisplay generator.image eval "PharoVMBuilder buildOnJenkins: '$OS'" || (cat stderr; exit 1) cd "$WORKSPACE" tar -czf sources.tar.gz -C cog . # Compile ==================================================================== cd cog/build sh build.sh # Archive ==================================================================== cd "$WORKSPACE/cog/results" zip -r "vm.zip" $ZIP_FILTER cp -f vm.zip ../../"${BUILD_NUMBER}.zip" cp -f vm.zip ../../"latest.zip" mv -f vm.zip ../../"Pharo-VM-${OS}-latest.zip" # success exit 0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versioning-Jenkins-Logic-tp4820056.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015