[Laszlo-user] oooh nice new debugging tool

[P T Withington]

[Resent to laszlo-user]

There is also a new checkbox on the dev console to enable backtraces,  
so if you forget, just check the box and hit compile to re-run your  
app with backtraces on.

All Debug.{write,debug,info,warn,error,format} calls capture a  
backtrace, so you can click on any such message to see where they  
were called.  Ditto if you use Debug.trace or Debug.monitor -- you  
can use those to figure out who is calling a method or modifying an  
attribute.

If you don't know it already, you can click on the elements of the  
stack trace to see their details.

On 2007-08-17, at 16:17 EDT, Benjamin Shine wrote:

>
> Henry just added this cool feature: turn on backtracing at  
> application compile-time:
> Add a flag to your lzx query "lzbacktrace=true" (also debug=true  
> because otherwise there's no point)
> then when you have an error, warning, or info in the debugger  
> window, click on it for more information, then - ahh - click on the  
> "backtrace" attribute. You will get a stack trace.
>
> This works in wafflecone starting with ultra-recent builds, as of  
> r6111.
>
> Rock, Henry!