June 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Seaside] Seaside 2.8.4 image crashes [newbie]
by Lukas Renggli June 10, 2009

June 10, 2009

This is certainly not your fault. It has probably to do with a missing plugin. I'll forward it to the Pharo list, maybe somebody knows more about this? I think I heard that problem before. Lukas On Tue, Jun 9, 2009 at 11:41 PM, Ivar Refsdal<refsdal.ivar(a)gmail.com> wrote: > Hello all, > > I'm a very fresh newbie, so the problem could just be myself. > Apologies in advance > if that is the case. However I'm getting a crash when doing the > following after starting Seaside with ./seaside.sh: > First going to http://localhost:8080/seaside/magritte/editor in a web browser, > then clicking 'Add' and then 'Save' without entering any data. > Then when clicking 'Preview' Seaside crashes with the following message: > > Segmentation fault > > 2022517340 UUID>initialize > 2022517224 Behavior>new: > 2022517132 >new > 2022517040 >uuid > 2022516948 >new > 2022516856 >defaultAccessor > 2022516764 MADescription>accessor > 2022516672 MADescription>hash > 2022516580 Dictionary>scanFor: > 2022516488 Set>findElementOrNil: > 2022516180 Dictionary>at:ifAbsent: > 2022516088 MAAdaptiveModel>readUsing: > 2022515996 MAMemento>pullRaw > 2022515840 OrderedCollection>do: > 2022515748 MAContainer>do: > 2022515656 MAMemento>pullRaw > 2022515564 MAMemento>pull > 2022515452 MACachedMemento>reset > 2022515360 MACheckedMemento>reset > 2022515268 >model:description: > 2022514976 MAContainer>asComponentOn: > 2022514884 Object>asComponent > 2022514792 MADescriptionEditor>preview > 2022514700 WASubmitButtonTag>on:of: > 2022514496 WAActionCallback>evaluateWithArgument: > 2022514036 WACallback>evaluateWithField: > 2022513760 WACallbackStream>processCallbacksWithOwner: > 2022509456 WAPresenter>processCallbackStream: > 2022509364 WAPresenter>processChildCallbacks: > 2022509272 WAComponent>decorationChainDo: > 2022509180 WAComponent>nextPresentersDo: > 2022509060 WAComponent>childrenDo: > 2022508968 SequenceableCollection>do: > 2022508836 WAComponent>childrenDo: > 2022508744 WAComponent>nextPresentersDo: > 2022508652 WAPresenter>processChildCallbacks: > 2022508560 WAPresenter>processCallbackStream: > 2022508392 WAToolFrame>processCallbackStream: > 2022508300 BlockClosure>on:do: > 2022508196 WAToolFrame>withDeprecatedHandlerDo: > 2022508104 WAToolFrame>processCallbackStream: > 2022508012 WARenderContinuation>processCallbacks: > 2022507884 WAComponent>decorationChainDo: > 2022504988 WARenderContinuation>processCallbacks: > 2022504896 WARenderContinuation>handleRequest: > 2022504804 BlockClosure>on:do: > 2022504712 WARenderContinuation>withNotificationHandler: > 2022504328 WARenderContinuation>handleRequest: > 2022501884 WASessionContinuation>value: > 2022501164 WASession>performRequest: > 2022501072 WASession>responseForRequest: > 2022500980 BlockClosure>on:do: > 2022500872 WASession>withErrorHandler: > 2022499892 BlockClosure>on:do: > 2022499800 WASession>withErrorHandler: > 2022499708 WASession>responseForRequest: > 2022499616 BlockClosure>on:do: > 2022499500 >use:during: > 2022499312 WASession>responseForRequest: > 2022499220 WASession>withEscapeContinuation: > 2022499128 >currentDo: > 2022499016 WASession>withEscapeContinuation: > 2022498904 WASession>responseForRequest: > 2022498812 WASession>incomingRequest: > 2022498548 BlockClosure>on:do: > 2022498456 WAProcessMonitor>critical:ifError: > 2022498364 BlockClosure>ensure: > 2022498272 WAProcessMonitor>critical:ifError: > 2022498640 BlockClosure>newProcess > Aborted > > I'm using this image file (no changes made): > http://www.seaside.st/distributions/Seaside-2.8.4.app.zip > Otherwise I'm on Ubuntu 9.04 i386, nothing special. Let me know if I > can provide more details. > I also tried executing the cleanup commands in the workspace, but it > didn't help. > The crash does not occur with the previous image I tried: Seaside-2.8-578.app. > > Any suggestions? > Thanks, > > Kind regards, > Ivar Refsdal > > (First post, hope everything went well.) > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Lukas Renggli http://www.lukas-renggli.ch

4 5

[Pharo-project] [ANN] New Unix/Linux VM
by Damien Cassou June 10, 2009

June 10, 2009

Hi, I've just published a new Unix/Linux VM based on Exupery-vm-0.15.1: - Rename root directory from 'build' to 'pharo-vm-0.15.1b' - Rename UUIDPlugin to UUIDPlugin.bak (issue #855) http://pharo-project.org/download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] new mailist?
by Jon Hancock June 10, 2009

June 10, 2009

I have to unsubscribe. This list is too active. It clogs downloading of my email. It would be wonderful if the list were run on something with more options such as google groups. thanks guys. look forward to pharo's continued growth. Jon

3 2

[Pharo-project] Syntax error loading Coral
by Luc Fabresse June 10, 2009

June 10, 2009

Hi all, I tried to load Coral in the latest dev image using ScriptLoader and I got a syntax error in "UnixProcess>>argsAsFlatArrayAndOffsets:". I guess it is an UTF-8 problem. Any ideas for a solution ? #Luc

6 11

[Pharo-project] Lost code
by Schwab,Wilhelm K June 10, 2009

June 10, 2009

I have at times been disappointed to see good coding effort get lost, both in browsers and the debugger. In the latter, it seems to happen when it warns about having to revert to a previous block or something along those lines. The browser loses are still mysterious to me - maybe it happens if code pane isn't properly associated with the selected class. Is there a way that the tools could keep a buffer of a few "accepts" worth of code to salvage such situations? Bill

2 1

[Pharo-project] new mailist?
by Torsten Bergmann June 10, 2009

June 10, 2009

Just login with email address at the bottom of [1] and edit the options so not all the emails get forwarded. This will still allow you to post but you can browse the list using the mailing list archive [2]. Bye Torsten [1] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project [2] http://lists.gforge.inria.fr/pipermail/pharo-project/ -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] vm-maker
by danil osipchuk June 10, 2009

June 10, 2009

Hello squeak people Does anyone have a hint how to get (with reasonable effort) current vmmaker setup? May be there is a prepared image somewhere? I'm interested in building vm on windows. When I follow these instructions: http://wiki.squeak.org/squeak/6102 i stuck during loading of vmmaker from the squeak-map regards, Danil

3 2

[Pharo-project] About EndOfStream notification [was Streams - #nextLine]
by Nicolas Cellier June 9, 2009

June 9, 2009

About this subject, here is a little reflexion explaining why Notification are not my preferred solution anymore (though I defended it at http://bugs.squeak.org/view.php?id=6755 ). If you remember animated discussions about EndOfStream, then you might say Oh no, not again! However, my opinion has evolved closer to Andreas' one. It still don't find == nil a good solution for generic Stream (though acceptable for character streams). Neither do I reject the idea of catching an EndOfStream : it can be efficient if the event is rare (in other words, if the stream is long, or if there are many wrappers, each testing == nil or atEnd). What I find a big mistake now is to generalize use of an Exception with a default action. I know, this default action is for backward compatibility (answer nil). But let's take an example showing how it can be bad: First load ConnectEndOfStream-M6755-nice.1.cs and RepeatUntil-M6755-nice.1.cs from http://bugs.squeak.org/view.php?id=6755 Then try this: | str sum buffer char | str := '123 456 798' readStream. sum := 0. buffer := WriteStream on: (String new: 16). [char := str next. char isSeparator ifTrue: [buffer isEmpty ifFalse: [sum := sum + buffer contents asNumber. buffer reset]] ifFalse: [buffer nextPut: char]] repeatUntil: EndOfStream. buffer isEmpty ifFalse: [sum := sum + buffer contents.]. ^sum Yes, it just split a string on separators, convert every packet into a number and sum the numbers. The example is silly, don't comment on that. There are plenty other ways to split a String. The problem is that the loop will stop after first number... What's going on? Well, asNumber uses a readStream to perform the conversion, reads past end, and signals an EndOfStream... That is bad... I should have protected the Exception handling with: | str sum buffer char | str := '123 456 798' readStream. sum := 0. buffer := WriteStream on: (String new: 16). [[char := str next. char isSeparator ifTrue: [buffer isEmpty ifFalse: [sum := sum + buffer contents asNumber. buffer reset]] ifFalse: [buffer nextPut: char]] repeat] on: EndOfStream do: [:exc | exc receiver == str ifTrue: [exc return] ifFalse: [exc pass]]. buffer isEmpty ifFalse: [sum := sum + buffer contents.]. ^sum Oh yes, easy. But imagine now that str is a wrapper on a FileStream... (for example an InflateStream). Exception handling soon becomes hard to write, because you might have to walk up the Context stack... There are better examples where I want Exceptions, so I'd like the choice to be in programmers hands. - 1) Raising an EndOfStream Exception (and not a Notification as I suggested) should be optional - 2) The Exception should not have a default action. The simple thing to do is to add an endOfStreamAction instanceVariable to Stream or ReadStream. If a read past end is attempted, then ^endOfStreamAction value. nil value = nil, so letting this inst var uninitialized will lead to backward compatibility (at minimal cost concerning efficieny!). filling the inst var with a block comes to mind immediately, and among natural choice is: Stream>>willSignalEndOfStream self endOfStreamAction: [EndOfStream signal] There might be more work for Stream wrappers, but that sounds a cheap and efficient idea to reconcile both worlds. What will protect above code example from an internal low level EndOfStream? Nothing, but the fact that programmers using explicitely #willSignalEndOfStream will know what they do! Either they will protect with a handling block, or advertise enough that the code might generate spurious EndOfStream on malformed inputs... Of course, I must remind: use Exception handling pattern but don't abuse. Programming with these deserve great care! Cheers Nicolas

3 9

[Pharo-project] [ANN] pre-built Core #10331
by Marcus Denker June 9, 2009

June 9, 2009

Hi, I put a new core image up: https://gforge.inria.fr/frs/download.php/22419/Pharo0.1Core-10331cl.zip ...with all the updates till #10331 Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

2 1

[Pharo-project] strange problem with tests
by Gabriel Brunstein June 9, 2009

June 9, 2009

I have a problem with some test cases. If I run them from the browser, they run successfully but if I run them from the test runner they fail sometimes but sometimes not. It is not a problem of process because there isn't any fork in the code. By the way, I checked the names of the process for both codes at all time and they are the same. What is more, if i add something like "Transcript show: 'something'" at the beginning of each method, they always run successfully. Any idea??

1 0