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

Re: [Pharo-project] Recover from an MNU in start up list?

by Craig Latta

> One way is in gdb put a breakpoint in the MNU processing > (createActualMessage). Or do it from the VM simulator. If you can't get it work, I'll take a stab at it. good luck, -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468

April 9, 2012

[Pharo-project] Using stdout in Windows --> 'File stdout is closed'

by Martin Dias

Hi In my windows 7, I get an error when trying to write to "FileStream stdout" in both Pharo 1.4 and 1.3 (revisions #14423 and #13320). To reproduce, - download: https://ci.lille.inria.fr/pharo/job/Pharo%201.4/373/artifact/Pharo-1.4.zip - evaluate: FileStream stdout nextPutAll: 'a'. Is this a known issue? I couldn't find it in issue tracker. Thanks in advance. MartÃn

April 8, 2012

Re: [Pharo-project] Recover from an MNU in start up list?

by Max Leske

For 1.3 see http://code.google.com/p/pharo/issues/detail?can=2&start=0&num=100&q=&colsp… For 1.4 I don't know. Max PS: Still working on a working fixâ¦ sorry for the delay but I'm trying to be thorough On 08.04.2012, at 23:26, Philippe Marschall wrote: > Hi > > I extracted a superclass and now I get a MNU during image startup because I have an instance of the now abstract base class in the start up list. > > The image comes up for a fraction of a second and the crashes (PharoDebug.log). Any idea of how I can recover from this? > > Cheers > Philippe > >

April 8, 2012

Re: [Pharo-project] Recover from an MNU in start up list?

by Eliot Miranda

On Sun, Apr 8, 2012 at 2:26 PM, Philippe Marschall <kustos(a)gmx.net> wrote: > Hi > > I extracted a superclass and now I get a MNU during image startup because > I have an instance of the now abstract base class in the start up list. > > The image comes up for a fraction of a second and the crashes > (PharoDebug.log). Any idea of how I can recover from this? > One way is in gdb put a breakpoint in the MNU processing (createActualMessage). Then when you hit the MNU edit the message object to something harmless such as Message selector: #class arguments: #(), and proceed. This isn't easy. You have to learn how to find symbols in the VM (you'll need to find eg. #class) and how to store pointers in an object. So only consider doing this if the image is worth a few hours learning arcane VM innards, and possibly building a debug VM that'll be less fragile in gdb. > Cheers > Philippe > > > -- best, Eliot

April 8, 2012

[Pharo-project] Recover from an MNU in start up list?

by Philippe Marschall

Hi I extracted a superclass and now I get a MNU during image startup because I have an instance of the now abstract base class in the start up list. The image comes up for a fraction of a second and the crashes (PharoDebug.log). Any idea of how I can recover from this? Cheers Philippe

April 8, 2012

Re: [Pharo-project] font reading problems

by Esteban Lorenzano

Hi, On Apr 8, 2012, at 9:43 PM, Guillermo Polito wrote: > I like monospace fonts mostly for programming... > > Courier new? courier sucks :P > DejaVu sans mono? +1 > > On Sun, Apr 8, 2012 at 9:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I do not like the default font because there is not enough space around : > so this is difficult to see it for example in > > := > > > > so what can be done? > Can we modify this font? > > Stef >

April 8, 2012

Re: [Pharo-project] font reading problems

by Guillermo Polito

I like monospace fonts mostly for programming... Courier new? DejaVu sans mono? On Sun, Apr 8, 2012 at 9:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > I do not like the default font because there is not enough space around : > so this is difficult to see it for example in > > := > > > > so what can be done? > Can we modify this font? > > Stef >

April 8, 2012

[Pharo-project] font reading problems

by StÃ©phane Ducasse

Hi guys I do not like the default font because there is not enough space around : so this is difficult to see it for example in := so what can be done? Can we modify this font? Stef

April 8, 2012

Re: [Pharo-project] Milestone reached :-)

by StÃ©phane Ducasse

Simply gorgeous! On Apr 8, 2012, at 6:23 PM, Pavel Krivanek wrote: > Hi, > > I created an experimental CI build that loads Fuel into the Pharo > Kernel, unloads Compiler and uses an special launcher that expects a > binary package name as command line argument. > > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Fuel/ > > You can test it with something like (see attachment): > > CogVM PharoKernel-Fuel-1.4.image testingPackage.fuel > > Following code exports a fuel binary package from the image: > > FileStream forceNewFileNamed: 'testingPackage.fuel' do: [:aStream | > aStream binary. > FLPackageStore new storeOn: aStream packageNamed: 'TestingPackage'.]. > > As you can see from the output of the testing class, there is no > Compiler class in the image. > > Cheers, > -- Pavel > <testingClassOutput.txt><TestingPackage.st><testingPackage.fuel>

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by Mark Smith

Great :). I hope you succeed in coaxing Sven to write a chapter. The more written down the better :). Mark. On 8 Apr 2012, at 17:48, StÃ©phane Ducasse wrote: > I'm trying to make sven write a chapter :) > So I added it to the server section :) > > Stef > >> Hi Sven, >> >> That makes a lot of sense :). >> >> Perhaps this could be added to the Getting Started section of the website? >> >> Thanks! >> >> Mark >> >> On 8 Apr 2012, at 17:11, Sven Van Caekenberghe wrote: >> >>> Mark, >>> >>> On 08 Apr 2012, at 16:11, Mark Smith wrote: >>> >>>> Hi all, >>>> >>>> Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? >>>> >>>> After the image starts up the server has an invalid socket handle. >>>> >>>> To reproduce, evaluate the following in a workspace, then save and quit the image. >>>> >>>> aServer := ZnServer on: 8080. >>>> aServer delegate: ((ZnMonticelloServerDelegate new) >>>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>>> aServer start >>>> >>>> Any ideas? >>>> >>>> Mark >>> >>> Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. >>> Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. >>> >>> To make this work, either change your example to >>> >>> aServer := ZnServer defaultOn: 8080. >>> aServer delegate: ((ZnMonticelloServerDelegate new) >>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>> aServer start >>> >>> or to >>> >>> aServer := ZnServer on: 8080. >>> aServer delegate: ((ZnMonticelloServerDelegate new) >>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>> aServer register. >>> aServer start >>> >>> It is by design that not every server is registered (as not everyone needs this behavior). >>> The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. >>> >>> HTH, >>> >>> Sven >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >> >> > >

April 8, 2012