[Seaside] Seaside 2.8a1-lr.518 - VW7.6 27 - weird thing happening

Philippe Marschall philippe.marschall at gmail.com
Tue Sep 2 18:07:18 UTC 2008


2008/9/2 Claus Kick <claus_kick at web.de>:
> Philippe Marschall wrote:
>>
>> 2008/9/1 Claus Kick <claus_kick at web.de>:
>>
>>> Philippe Marschall wrote:
>>>
>>>> Looks, interesting, like something in the backtracking mechanism is
>>>> broken. Are all applications broken? Can you post a are detailed stack
>>>> trace, eg. open a debugger?
>>>>
>>>> Cheers
>>>> Philippe
>>>
>>> Hello Philippe,
>>>
>>> sorry, forgot about the debugger, my bad.
>>>
>>> - the Dispatcher still works
>>> - I can still open config , but configuring anything yields a walkback
>>>
>>> At first I figured my own application was configured the wrong way, so I
>>> tried to remove it, but this does not work either (i.e. returns a
>>> walkback).
>>
>>
>> Removing returns a walkback?
>
> Yes it does as  follows:
>
> Possible Causes
>
>    * you sent a message this type of object doesn't understand
>
> Stack Trace
>
>   1.
>
>      thisContext
>          Seaside.WAValueHolder(Object)>>doesNotUnderstand:
>      self
>          a Seaside.WAValueHolder contents: false
>      aMessage
>          a Message with selector: #restore: and arguments: #(a
> Seaside.WAValueHolder contents: false)
>      excpt
>          a MessageNotUnderstood
>      resumeValue
>          nil
>
>   2.
>
>      thisContext
>          Seaside.WAValueHolder(Object)>>restoreFrom:
>      self
>          a Seaside.WAValueHolder contents: false
>      aMemento
>          a Seaside.WAValueHolder contents: false
>
>   3.
>
>      thisContext
>          Seaside.WAValueHolder(Object)>>restoreFromSnapshot:
>      self
>          a Seaside.WAValueHolder contents: false
>      anObject
>          a Seaside.WAValueHolder contents: false
>
>   4.
>
>      thisContext
>          optimized [] in Seaside.WASnapshot>>restore
>      self
>          BlockClosure [] in Seaside.WASnapshot>>restore
>      key
>          a Seaside.WAValueHolder contents: false
>      value
>          a Seaside.WAValueHolder contents: false
>
>   5.
>
>      thisContext
>          Seaside.WASnapshot(IdentityDictionary)>>keysAndValuesDo:
>      self
>          Seaside.WASnapshot (a Seaside.WAValueHolder contents: false->a
> Seaside.WAValueHolder contents: false...etc...
>      aBlock
>          BlockClosure [] in Seaside.WASnapshot>>restore
>      index
>          3
>      key
>          a Seaside.WAValueHolder contents: false
>
>>> - my own app crashes (ok, very likely that I have an error in there, but
>>> still get about the same - to me mystic -  walkback which does not
>>> include
>>> anything from my code)
>>
>>
>> Can you describe crash a little bit more in detail.
>
> Well, I get a similar looking walkback, that is:
>
> Possible Causes
>
>    * you sent a message this type of object doesn't understand
>
> Stack Trace
>
>   1.
>
>      thisContext
>          Seaside.WAValueHolder(Object)>>doesNotUnderstand:
>      self
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>      aMessage
>          a Message with selector: #restore: and arguments: #(a
> Seaside.WAValueHolder contents: a Seaside.WAToolFrame)...etc...
>      excpt
>          a MessageNotUnderstood
>      resumeValue
>          nil
>
>   2.
>
>      thisContext
>          Seaside.WAValueHolder(Object)>>restoreFrom:
>      self
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>      aMemento
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>
>   3.
>
>      thisContext
>          Seaside.WAValueHolder(Object)>>restoreFromSnapshot:
>      self
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>      anObject
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>
>   4.
>
>      thisContext
>          optimized [] in Seaside.WASnapshot>>restore
>      self
>          BlockClosure [] in Seaside.WASnapshot>>restore
>      key
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>      value
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>
>   5.
>
>      thisContext
>          Seaside.WASnapshot(IdentityDictionary)>>keysAndValuesDo:
>      self
>          Seaside.WASnapshot (a Seaside.WAValueHolder contents: a
> Seaside.WAToolFrame->a Seaside.WAValueHolder...etc...
>      aBlock
>          BlockClosure [] in Seaside.WASnapshot>>restore
>      index
>          2
>      key
>          a Seaside.WAValueHolder contents: a Seaside.WAToolFrame
>
>>> - tests breaks
>>> - tools breaks
>>> - examples also breaks
>>
>>
>> What do you mean with break?
>
> Walkbacks, similar to the two mentioned above.

I had a look again and this looks not like a configuration issue. It
looks more like something in the core of the Seaside backtracking
mechanism is broken. The code seems to be quite different from Squeak
as well. Are you sure you changed no Seaside code?

Cheers
Philippe


More information about the seaside mailing list