[Seaside] Enlarge the stack trace for debugging deployed application

[John McKeon]

On Thu, Jun 25, 2009 at 3:05 PM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> 2009/6/25 Zirbler <cj-bachinger at gmx.de>:
> >
> > Hi,
> >
> > I have to debug a deployed version of a Seaside 2.8 application under
> > Dolphin Smalltalk. Starting Firefox on http://localhost:8888/seaside I
> look
> > at the stack trace below. But to see the real error I need a larger stack
> > trace. Is there any way to do that changing code in WAWalkback.
>
> Clicking the "Full Stack" link should do the trick.


That would be the case if something other than WAWalkBack were the source of
the error. When WAWalkBack throws a DNU you get the plain text stack trace
without all the helpful links. This looks alot like the bug that was
corrected with the Seaside2.8a1-lr591 update - but not quite. Since its the
Dolphin port I am unable to comment further other than you should look at
WAWalkBack>>renderStackFrameOn: and see why aContext is a StackFrame object
and not a MethodContext or some other sublclass of ContextPart. Once you get
past that then you will get the usual walkback that will point to the real
problem

HTH
John


>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
http://jmck.seasidehosting.st
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20090625/1f27af0a/attachment.htm