Re: [Help-smalltalk] Swazoo, Seaside and gst

[nico]

I finally found a way to see the backtrace!

gst-remote -I nico.im --server --start=Seaside

Now gst doesn't crash and show the error :)
(BTW, what's the difference with starting seaside by hand? Why doesn't
it crash now?)

So, there was a very small bug in SwazooBuffer, see the attached patch.
The Seaside multiform functional test still doesn't work (the response
doesn't have _s and _k fields) but at least it doesn't crash.

I'll try to see what's the problem now :)

Cheers!

Nico

Le samedi 07 février 2009 à 15:43 +0100, Paolo Bonzini a écrit :
> > From my point of view (a squeaker ;)) one strange thing is that
adding a
> > halt at any place of a request processing in Swazoo makes gst crash.
> 
> I don't know... Does it spit out a backtrace?
> 
> > Is there a reason for this? What is the best way to debug it then?
> 
> printNl works great. :-)
> 
> > I also saw that seaside request processing runs inside an exception
> > block.
> 
> That's the same as upstream Seaside, I didn't change anything.
> 
> Paolo

HTTP_signsOfBoundaryFix.patch
Description: Text Data

signature.asc
Description: Ceci est une partie de message numériquement signée