Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Lukas Renggli
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<[hidden email]> 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
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Schwab,Wilhelm K
On Ubuntu 9.04, find the UUIDPlugin folder and rename the _folder_ to something like UUIDPlugin-not-used and all should be well.



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Lukas Renggli
Sent: Tuesday, June 09, 2009 4:47 PM
To: Seaside - general discussion
Cc: Pharo Development
Subject: Re: [Pharo-project] [Seaside] Seaside 2.8.4 image crashes [newbie]

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<[hidden email]> 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
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Adrian Lienhard
In reply to this post by Lukas Renggli
Yes, this is a bug in the Unix VM. See the following issue, which  
describes a workaround:

http://code.google.com/p/pharo/issues/detail?id=855

HTH,
Adrian

On Jun 9, 2009, at 23:46 , Lukas Renggli wrote:

> 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<[hidden email]> 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
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Damien Cassou
In reply to this post by Lukas Renggli
On Tue, Jun 9, 2009 at 11:46 PM, Lukas Renggli<[hidden email]> wrote:
> 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.

Please download the new VM which includes the work-around for this bug:

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

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Lukas Renggli
>> I'll forward it to the Pharo list, maybe somebody knows more about
>> this? I think I heard that problem before.
>
> Please download the new VM which includes the work-around for this bug:
>
> http://pharo-project.org/download

I used that VM. Or did you just update?

Lukas


>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] Seaside 2.8.4 image crashes [newbie]

Damien Cassou
On Wed, Jun 10, 2009 at 11:56 AM, Lukas Renggli<[hidden email]> wrote:
>>> I'll forward it to the Pharo list, maybe somebody knows more about
>>> this? I think I heard that problem before.
>>
>> Please download the new VM which includes the work-around for this bug:
>>
>> http://pharo-project.org/download
>
> I used that VM. Or did you just update?

I've changed where the link 'Gnu/Linux and other unix' points to. It
now points to a new zip file which is based on exupery-0.15.1 and has
the following changes:

- Rename root directory from 'build' to 'pharo-vm-0.15.1b'
- Rename UUIDPlugin to UUIDPlugin.bak (issue #855)

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project