- Pharo-users - lists.pharo.org

Re: [Pharo-users] Issue on Seaside beginning

by serge.stinckwich＠gmail.com

Nice Cheikhou to see you there ! I hope your enjoy the MOOC. See you soon Sent from my iPhone > On 4 juin 2016, at 19:58, Cheikhou Oumar KA <cheikhouka(a)gmail.com> wrote: > > Hi Stef > > > You got a problem with such image > > > https://ci.inria.fr/pharo-contribution/job/PharoWeb/PHARO=50,VERSION=stable… > > Yes I saved my code in Smalltalkhub. i loaded it in this new image and It works perfectly. > May be there the problem come from the combination of seaside and teapot in the same package....don't know. > > >Sorry for the inconvenience. > > Don't worry. Thanks a lot. Now I can poursue my exercises. > > Thanks > > > > > 2016-06-04 18:06 GMT+00:00 stepharo <stepharo(a)free.fr>: >> Hi Cheikhou >> >> We will have a look. I will contact Luc and Damien because I do not follow the Seaside set up. >> May be we messed up with the setup of the seaside image we gave you. >> Did you save your code? >> >> So that you can reload it with the >> https://ci.inria.fr/pharo-contribution/job/Seaside/ >> >> Seaside3.2 >> >> >> You got a problem with such image >> >> https://ci.inria.fr/pharo-contribution/job/PharoWeb/PHARO=50,VERSION=stable… >> >> do you have your code published so that I try to reproduce your problem? >> >> Sorry for the inconvenience. >> >> Stef >>> Le 4/6/16 Ã 19:00, Cheikhou Oumar KA a Ã©crit : >>> Hello. >>> >>> I am following #PharoMOOC and it become more and more exciting. >>> >>> I were doing TinyBlog exercise and I got an issue. I looked at the forum but any solution and I am stuck now like many others. >>> >>> I have created my class TBApplicationRootComponent, create a server that listen at :8080 and start it, regiser my application.... >>> >>> But at http://localhost:8080/browse I got this Image in my browser >>> <mime-attachment.png> >>> >>> Any help is welcome. >>> >>> Thanks >>> >>> -- >>> Cheikhou Oumar KA >>> å¥¥ é©¬ å° Â·è°¢ èµ« Â·å >>> Doctorant Informatique >>> cheikhouka(a)gmail.com > > > > -- > Cheikhou Oumar KA > å¥¥ é©¬ å° Â·è°¢ èµ« Â·å > Doctorant Informatique > cheikhouka(a)gmail.com > > >

June 5, 2016

Re: [Pharo-users] Issue on Seaside beginning

by stepharo

Ok > Hi Stef > > > You got a problem with such image > > > > https://ci.inria.fr/pharo-contribution/job/PharoWeb/PHARO=50,VERSION=stable… > > Yes I saved my code in Smalltalkhub. i loaded it in this new image and > It works perfectly. > > May be there the problem come from the combination of seaside and > teapot in the same package....don't know. > > >Sorry for the inconvenience. > > Don't worry. Thanks a lot. Now I can poursue my exercises. > Super. We spend really a lot of time on this mooc :) BTW we are working on an extra chapter to explain on to produce a REST API and it is nice simple and powerful. Stef

June 5, 2016

Re: [Pharo-users] problem getting moose

by stepharo

Hi ben I got some similar behavior when the network is not good. We should improve the loading of packages but this is simple than actually having a bullet proof solution. It is a couple of years that I think about it: loading in a separate environment and on crash do not install Stef Le 5/6/16 Ã 08:18, Ben Coman a Ã©crit : > On Sun, Jun 5, 2016 at 1:34 PM, Ben Coman <btc(a)openinworld.com> wrote: >> I wanted to try out Peter's XMI Analyser with Roassal and went to >> download Moose but had a couple of problems. >> >> First try... >> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) >> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but >> got a problem - big pause, no progress bars, the later ZipArchive >> reporting "Error: can't find EOCD position" >> >> Second try... >> The web site advises for Moose 6.0 to download the Moose code in a >> Pharo 5.0 image per... >> Gofer new >> smalltalkhubUser: 'Moose' project: 'Moose'; >> configuration; >> loadDevelopment. >> >> Doing that in build 50760 download with the Launcher produced... >> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in >> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache >> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could >> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8: >> Illegal leading byte for utf-8 encoding' >> >> Could someone check if they see the same, or maybe my Internet is flakey atm? >> (preferably someone who doesn't normally use Moose to avoid package >> cache differences) > More info.. > > The repository defined in Monticello is > MCSqueaksourceRepository > location: 'http://www.squeaksource.com/phexample' > user: '' > password: '' > which I could not open, again getting... > MCRepositoryError: Could not access > http://www.squeaksource.com/phexample: ZnInvalidUTF8: Illegal leading > byte for utf-8 encoding > > I tried changing to... > MCHttpRepository > location: 'http://www.squeaksource.com/phexample' > user: '' > password: '' > with no luck. > > But from Monticello I can define and successfully open another repository... > MCHttpRepository > location: 'http://www.squeaksource.com/DavidLightsOut' > user: '' > password: '' > > The top of stack is... > "a MetacelloFetchingMCSpecLoader(atomic load : 4.4-beta.1 [ConfigurationOfMoose] > load : Filesystem-tg.85 > load : Nile-Base-DamienCassou.81)" > > btw, > Phexample-NikoSchwarz.57 (2010-10-26) seems quite old, > with the latest on Squeaksource being Phexample-NikoSchwarz.63.mcz2011-08-29; > latest on Smalltalkhub/PharoExtras/Phexample being > Phexample-Core-CamilloBruni.67 (05/03/2013); > latest on Smalltalk/Phexample/Phexample being > Phexample-DenisKudryashov.75 (08/04/2016) > > cheers -ben > >

June 5, 2016

Re: [Pharo-users] problem getting moose

by Ben Coman

Final thing... after loading, the following packages are dirty... AST-Core - removal of NumberParser>>#isNumber: Collections-Abstract - but when checked ==> no changes Famix-Core - but when checked ==> no changes Rubric-Rules - but when checked ==> no changes cheers -ben

June 5, 2016

Re: [Pharo-users] Pharo 5 hanging and crashing

by stepharo

Hi Gerry I really really want to thank you for such reports. Because we do not have crashes like that on any of our machines. Now since some months we are looking for a bug related to fonts and FFI. Our main problem is how to reproduce it. What I suggest is - try Pharo 40, it is really stable and there is not much difference. It will lower your frustration - if you want to help us could you let us know if Pharo 60 alpha is working for you? We will check with Esteban if he can do some coding sessions with the OS you mention. Stef Le 4/6/16 Ã 23:48, Gerry Weaver a Ã©crit : > > Hello All, > > I am new to Pharo and Smalltalk in general. I have been experimenting > with Pharo 5 trying to get acquainted with the environment and the > language. I have been having some issues with the image hanging and > crashing. This happens when trying code in the Play Ground and > especially when stepping through code in the debugger. Has anyone had > similar problems? Should I be using Pharo 4 instead? > > I have been testing Pharo on Windows 8 64bit and Ubuntu 14.04 64bit. > Could this be a 64bit issue? > > Thanks >

June 5, 2016

Re: [Pharo-users] problem getting moose

by Ben Coman

>> On Jun 5, 2016, at 8:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >>> On Jun 5, 2016, at 7:34 AM, Ben Coman <btc(a)openInWorld.com> wrote: >>> >>> I wanted to try out Peter's XMI Analyser with Roassal and went to >>> download Moose but had a couple of problems. >>> >>> First try... >>> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) >>> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but >>> got a problem - big pause, no progress bars, the later ZipArchive >>> reporting "Error: can't find EOCD positionâ >> >> You can download the image as well: >> https://ci.inria.fr/moose/job/moose-6.0/lastSuccessfulBuild/artifact/moose-… >> >> >>> Second try... >>> The web site advises for Moose 6.0 to download the Moose code in a >>> Pharo 5.0 image per... >>> Gofer new >>> smalltalkhubUser: 'Moose' project: 'Moose'; >>> configuration; >>> loadDevelopment. >> >> Indeed, this is what the CI job does. >> >>> Doing that in build 50760 download with the Launcher produced... >>> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in >>> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache >>> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could >>> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8: >>> Illegal leading byte for utf-8 encodingâ >> >> Strange. If you download the Moose image, you get the SmalltalkHub repo: >> MCSmalltalkhubRepository >> owner: 'Phexample' >> project: 'Phexample' >> user: '' >> password: '' >> >>> Could someone check if they see the same, or maybe my Internet is flakey atm? >>> (preferably someone who doesn't normally use Moose to avoid package >>> cache differences) >> >> I am trying right now. >> >> Doru On Sun, Jun 5, 2016 at 2:47 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I figured out the problem. When you run that script, you actually load "4.4-beta.1 [ConfigurationOfMoose]â > > This is because of the mismatch between what loadDevelopment means in Gofer and the meaning of the symbolic version in Metacello. > > Instead, please use this: > > Metacello new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration: 'Moose'; > version: #development; > load. > > I also updated the Moose webpage. > > Cheers, > Doru Thanks Doru. That appears to have worked. Although an error popped up... SubclassResponsibility: AnObsoleteRubShoutStylerDecorator class had the subclass responsibility to implement #key Maybe because I had a Playground, Monticello & Pharo 5.0 Welcome windows open when I ran it. I tried again in a fresh image, running it from the old Workspace and that error did not occur, but when I choose World > Playground I get... MessageNotUnderstood: receiver of "beForSmalltalkScripting" is nil UndefinedObject(Object)>>doesNotUnderstand: #beForSmalltalkScripting RubSmalltalkScriptingMode>>updateTextAreaWhenPlugged RubSmalltalkScriptingMode(RubEditingMode)>>plugin: RubEditingArea(RubAbstractTextArea)>>editingMode: RubEditingArea>>beForSmalltalkScripting RubScrolledTextMorph>>beForSmalltalkScripting GLMMorphicPharoScriptRenderer>>morph GLMMorphicPharoScriptRenderer(GLMMorphicRubricTextRenderer)>>render: GLMMorphicPharoScriptRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderPharoScriptPresentation: GLMPharoScriptPresentation>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: [ self renderObject: each ] in [ :each | tabs addLazyPage: [ self renderObject: each ] label: (self titleOrIconOf: each in: tabs) toolbar: (self renderToolbarForPresentation: each inMorph: tabs) action: (self labelActionBrickFor: each) ] in GLMMorphicTabbedRenderer>>render: LazyTabPage>>actualPageMorph LazyTabGroupMorph>>pageAt: LazyTabGroupMorph>>updatePageIndex: LazyTabGroupMorph(TabGroupMorph)>>update: LazyTabGroupMorph(Object)>>update:with: MorphChangedWithArguments>>deliverTo: LazyTabGroupMorph(Morph)>>handleUpdate: MessageSend>>value: MessageSend>>cull: MessageSend>>cull:cull: [ action cull: anAnnouncement cull: announcer ] in AnnouncementSubscription>>deliver: BlockClosure>>on:do: BlockClosure>>on:fork: AnnouncementSubscription>>deliver: [ subscription deliver: anAnnouncement ] in SubscriptionRegistry>>deliver:to:startingAt: BlockClosure>>ifCurtailed: SubscriptionRegistry>>deliver:to:startingAt: SubscriptionRegistry>>deliver:to: SubscriptionRegistry>>deliver: Announcer>>announce: GLMTabSelectorBrick(Morph)>>doAnnounce: GLMTabSelectorBrick(Morph)>>changed:with: GLMTabSelectorBrick>>selectedIndex: LazyTabGroupMorph(TabGroupMorph)>>selectedPageIndex: [ tabs selectedPageIndex: index ] in GLMMorphicTabbedRenderer>>render: BlockClosure>>ensure: GLMAnnouncer>>suspendAllWhile: GLMMorphicTabbedRenderer>>render: GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderTabbedCompositePresentation: GLMTabbedArrangement>>renderGlamorouslyOn: GLMCompositePresentation>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicPaneRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicPaneRenderer>>renderContainerFor: GLMMorphicPaneRenderer>>render: GLMMorphicPaneRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderPane: GLMPane>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicPagerRenderer(GLMMorphicWidgetRenderer)>>renderObject: [ :each | container brickRoot pushPane: (self renderObject: each) ] in GLMMorphicPagerRenderer>>render: OrderedCollection>>do: GLMMorphicPagerRenderer>>render: GLMMorphicPagerRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderPager: GLMPager>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: GLMMorphicTabbedRenderer>>render: GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderTabbedCompositePresentation: GLMTabbedArrangement>>renderGlamorouslyOn: GTInspector(GLMCompositePresentation)>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: GLMMorphicTabbedRenderer>>render: GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderTabbedCompositePresentation: GLMTabbedArrangement>>renderGlamorouslyOn: GTPlayground(GLMCompositePresentation)>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicWindowRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicWindowRenderer>>render: GLMMorphicWindowRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>open: GTPlayground(GLMCompositePresentation)>>openWith: GTPlayground(GLMCompositePresentation)>>openOn:with: GTPlayground(GLMCompositePresentation)>>openOn: GTPlayground>>openOn: GTPlayground class(GLMCompositePresentation class)>>openOn: GTPlayground class>>open PharoCommonTools(ToolRegistry)>>openWorkspace A hack workaround was to commenting-out as follows... RubSmalltalkScriptingMode>>updateTextAreaWhenPlugged super updateTextAreaWhenPlugged. "self textArea shoutStyler beForSmalltalkScripting" Loading this fixes it... Name: Rubric-PavelKrivanek.370 Author: PavelKrivanek Time: 30 May 2016, 10:00:45.805722 am UUID: 8c58b690-fd8f-44e7-abba-468218ec4658 Ancestors: Rubric-TheIntegrator.369, Rubric-AlexandreBergel.369 - issue 18349: add method comment Loading this breaks it again... Name: Rubric-PavelKrivanek.371 uthor: PavelKrivanek Time: 31 May 2016, 1:38:35.400467 pm UUID: 9d7bfec6-9b4d-494b-a84b-079125e9fce4 Ancestors: Rubric-PavelKrivanek.370 move styling (Shout) support to standalone package cheers -ben

June 5, 2016

Re: [Pharo-users] problem getting moose

by Tudor Girba

Hi, I figured out the problem. When you run that script, you actually load "4.4-beta.1 [ConfigurationOfMoose]â This is because of the mismatch between what loadDevelopment means in Gofer and the meaning of the symbolic version in Metacello. Instead, please use this: Metacello new smalltalkhubUser: 'Moose' project: 'Moose'; configuration: 'Moose'; version: #development; load. I also updated the Moose webpage. Cheers, Doru > On Jun 5, 2016, at 8:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Jun 5, 2016, at 7:34 AM, Ben Coman <btc(a)openInWorld.com> wrote: >> >> I wanted to try out Peter's XMI Analyser with Roassal and went to >> download Moose but had a couple of problems. >> >> First try... >> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) >> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but >> got a problem - big pause, no progress bars, the later ZipArchive >> reporting "Error: can't find EOCD positionâ > > You can download the image as well: > https://ci.inria.fr/moose/job/moose-6.0/lastSuccessfulBuild/artifact/moose-… > > >> Second try... >> The web site advises for Moose 6.0 to download the Moose code in a >> Pharo 5.0 image per... >> Gofer new >> smalltalkhubUser: 'Moose' project: 'Moose'; >> configuration; >> loadDevelopment. > > Indeed, this is what the CI job does. > >> Doing that in build 50760 download with the Launcher produced... >> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in >> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache >> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could >> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8: >> Illegal leading byte for utf-8 encodingâ > > Strange. If you download the Moose image, you get the SmalltalkHub repo: > MCSmalltalkhubRepository > owner: 'Phexample' > project: 'Phexample' > user: '' > password: '' > >> Could someone check if they see the same, or maybe my Internet is flakey atm? >> (preferably someone who doesn't normally use Moose to avoid package >> cache differences) > > I am trying right now. > > Doru > >> cheers -ben >> > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

June 5, 2016

Re: [Pharo-users] problem getting moose

by Tudor Girba

Hi, > On Jun 5, 2016, at 7:34 AM, Ben Coman <btc(a)openInWorld.com> wrote: > > I wanted to try out Peter's XMI Analyser with Roassal and went to > download Moose but had a couple of problems. > > First try... > In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) > fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but > got a problem - big pause, no progress bars, the later ZipArchive > reporting "Error: can't find EOCD positionâ You can download the image as well: https://ci.inria.fr/moose/job/moose-6.0/lastSuccessfulBuild/artifact/moose-… > Second try... > The web site advises for Moose 6.0 to download the Moose code in a > Pharo 5.0 image per... > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration; > loadDevelopment. Indeed, this is what the CI job does. > Doing that in build 50760 download with the Launcher produced... > Could not resolve: Phexample [Phexample-NikoSchwarz.57] in > /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache > http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could > not access http://www.squeaksource.com/phexample: ZnInvalidUTF8: > Illegal leading byte for utf-8 encodingâ Strange. If you download the Moose image, you get the SmalltalkHub repo: MCSmalltalkhubRepository owner: 'Phexample' project: 'Phexample' user: '' password: '' > Could someone check if they see the same, or maybe my Internet is flakey atm? > (preferably someone who doesn't normally use Moose to avoid package > cache differences) I am trying right now. Doru > cheers -ben > -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

June 5, 2016

Re: [Pharo-users] problem getting moose

by Ben Coman

On Sun, Jun 5, 2016 at 1:34 PM, Ben Coman <btc(a)openinworld.com> wrote: > I wanted to try out Peter's XMI Analyser with Roassal and went to > download Moose but had a couple of problems. > > First try... > In the Launcher under Common Tools, I downloaded and Moose 5.1(stable) > fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but > got a problem - big pause, no progress bars, the later ZipArchive > reporting "Error: can't find EOCD position" > > Second try... > The web site advises for Moose 6.0 to download the Moose code in a > Pharo 5.0 image per... > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration; > loadDevelopment. > > Doing that in build 50760 download with the Launcher produced... > Could not resolve: Phexample [Phexample-NikoSchwarz.57] in > /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache > http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could > not access http://www.squeaksource.com/phexample: ZnInvalidUTF8: > Illegal leading byte for utf-8 encoding' > > Could someone check if they see the same, or maybe my Internet is flakey atm? > (preferably someone who doesn't normally use Moose to avoid package > cache differences) More info.. The repository defined in Monticello is MCSqueaksourceRepository location: 'http://www.squeaksource.com/phexample' user: '' password: '' which I could not open, again getting... MCRepositoryError: Could not access http://www.squeaksource.com/phexample: ZnInvalidUTF8: Illegal leading byte for utf-8 encoding I tried changing to... MCHttpRepository location: 'http://www.squeaksource.com/phexample' user: '' password: '' with no luck. But from Monticello I can define and successfully open another repository... MCHttpRepository location: 'http://www.squeaksource.com/DavidLightsOut' user: '' password: '' The top of stack is... "a MetacelloFetchingMCSpecLoader(atomic load : 4.4-beta.1 [ConfigurationOfMoose] load : Filesystem-tg.85 load : Nile-Base-DamienCassou.81)" btw, Phexample-NikoSchwarz.57 (2010-10-26) seems quite old, with the latest on Squeaksource being Phexample-NikoSchwarz.63.mcz2011-08-29; latest on Smalltalkhub/PharoExtras/Phexample being Phexample-Core-CamilloBruni.67 (05/03/2013); latest on Smalltalk/Phexample/Phexample being Phexample-DenisKudryashov.75 (08/04/2016) cheers -ben

June 5, 2016

Re: [Pharo-users] Pharo 5 hanging and crashing

by Gerry Weaver

Hi, I'm using the term "hanging" to mean that the image locked up or became unresponsive. When I use the term "crashing", I mean the image aborted. I have also seen a few cases where the image would hang first and then abort a few seconds later. This usually results after a few error windows have popped up. I'll try to keep track of when it happens again. Thanks -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Tudor Girba Sent: Sunday, June 5, 2016 12:55 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Pharo 5 hanging and crashing Hi, This is certainly not something that should happen. Pharo 5 is deemed ready for production and many of us are using it since a long time :). It is still possible that you encountered a bug, and having a reproducible case can help us spot it. Meanwhile, when you say crashing, do you mean that a debugger appeared, or that the image completely quitted? Was it because of a code that you run, or was it because of the interaction with tools? Cheers, Doru > On Jun 5, 2016, at 3:42 AM, Gerry Weaver <gerryw(a)compvia.com> wrote: > > Hi, > > I'm afraid I don't have any steps to reproduce the issues at the moment. I was just playing around and it hung or crashed frequently enough that it became a bit tedious. I just wondered, if anyone else was having problems. It would seem that I may be alone in this, so I'll try to figure out what is going on. > > Thanks > > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Tudor Girba > Sent: Saturday, June 4, 2016 4:56 PM > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Pharo 5 hanging and crashing > > Hi, > > Pharo 5 is the current release, and you should use this one :). > > Do you have a specific scenario that we can use to reproduce the crashing behavior? > > Cheers, > Doru > > >> On Jun 4, 2016, at 11:48 PM, Gerry Weaver <gerryw(a)compvia.com> wrote: >> >> Hello All, >> >> I am new to Pharo and Smalltalk in general. I have been experimenting with Pharo 5 trying to get acquainted with the environment and the language. I have been having some issues with the image hanging and crashing. This happens when trying code in the Play Ground and especially when stepping through code in the debugger. Has anyone had similar problems? Should I be using Pharo 4 instead? >> >> I have been testing Pharo on Windows 8 64bit and Ubuntu 14.04 64bit. Could this be a 64bit issue? >> >> Thanks > > -- > www.tudorgirba.com > www.feenk.com > > "What we can governs what we wish." > > > > > > -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

June 5, 2016