Enlarge the stack trace for debugging deployed application

6 messages Options
Embed this post
Permalink
Zirbler

Enlarge the stack trace for debugging deployed application

Reply Threaded More More options
Print post
Permalink
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.

thanks in forward
cjb

---- Start of Stack Trace ----

 Internal Error


   StackFrame does not understand #tempNames

a MessageNotUnderstood('StackFrame does not understand #tempNames')

StackFrame(Object)>>doesNotUnderstand:
[] in WAWalkback>>renderStackFrame:on:
BlockClosure>>renderOn:
[] in WAGenericTag(WATagBrush)>>with:
BlockClosure>>renderOn:
WARenderCanvas(WACanvas)>>nest:
WAGenericTag(WABrush)>>with:
WAGenericTag(WATagBrush)>>with:
WARenderCanvas(WAHtmlCanvas)>>definitionList:
WAWalkback>>renderStackFrame:on:
[] in WAWalkback>>renderStackOn:
BlockClosure>>renderOn:
[] in WAGenericTag(WATagBrush)>>with:
BlockClosure>>renderOn:
WARenderCanvas(WACanvas)>>nest:
WAGenericTag(WABrush)>>with:
WAGenericTag(WATagBrush)>>with:
WARenderCanvas(WAHtmlCanvas)>>listItem:
[] in WAWalkback>>renderStackOn:
OrderedCollection>>do:

---- End of Stack Trace -----
Philippe Marschall

Re: Enlarge the stack trace for debugging deployed application

Reply Threaded More More options
Print post
Permalink
2009/6/25 Zirbler <[hidden email]>:
>
> 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.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
John McKeon-2

Re: Enlarge the stack trace for debugging deployed application

Reply Threaded More More options
Print post
Permalink


On Thu, Jun 25, 2009 at 3:05 PM, Philippe Marschall <[hidden email]> wrote:
2009/6/25 Zirbler <[hidden email]>:
>
> 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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



--
http://jmck.seasidehosting.st

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Philippe Marschall

Re: Enlarge the stack trace for debugging deployed application

Reply Threaded More More options
Print post
Permalink
2009/6/25 John McKeon <[hidden email]>:

>
>
> On Thu, Jun 25, 2009 at 3:05 PM, Philippe Marschall
> <[hidden email]> wrote:
>>
>> 2009/6/25 Zirbler <[hidden email]>:
>> >
>> > 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

You're right of course.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Zirbler

Re: Enlarge the stack trace for debugging deployed application

Reply Threaded More More options
Print post
Permalink
In reply to this post by John McKeon-2
Hi John,

where to find more information about Seaside2.8a1-lr591 update. I couldn't find nothing detailed in the web.

thanks
cjb

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

> 2009/6/25 Zirbler <cj-bachinger@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@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



--
http://jmck.seasidehosting.st

_______________________________________________
seaside mailing list
seaside@lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Lukas Renggli

Re: Enlarge the stack trace for debugging deployed application

Reply Threaded More More options
Print post
Permalink
Search for "[ANN]" in this mailing-list, e.g.
<http://lists.squeakfoundation.org/pipermail/seaside/2009-June/020869.html>
and <http://lists.squeakfoundation.org/pipermail/seaside/2009-June/021015.html>.

Lukas

On Mon, Jun 29, 2009 at 10:08 AM, Zirbler<[hidden email]> wrote:

>
> Hi John,
>
> where to find more information about Seaside2.8a1-lr591 update. I couldn't
> find nothing detailed in the web.
>
> thanks
> cjb
>
>
> John McKeon-2 wrote:
>>
>> On Thu, Jun 25, 2009 at 3:05 PM, Philippe Marschall <
>> [hidden email]> wrote:
>>
>>> 2009/6/25 Zirbler <[hidden email]>:
>>> >
>>> > 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
>>> [hidden email]
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>
>>
>>
>> --
>> http://jmck.seasidehosting.st
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Enlarge-the-stack-trace-for-debugging-deployed-application-tp24200417p24250006.html
> Sent from the Squeak - Seaside mailing list archive at Nabble.com.
>
> _______________________________________________
> 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