Thanks Fabian, This is helpful. And can be called easily from the console window.
I meant "call stack" instead of "stack trace" Here is the issue with Firebug: http://code.google.com/p/fbug/issues/detail?id=23&can=2&q= The more of us vote for it, the sooner will be fixed. Fabian Jakobs-2 wrote: > > if you know where the error occurs you can add a call to printStackTrace > at the position where you want to see the stack trace: > > this.printStackTrace(); > > This function is new in 0.7 and is defined here: > http://demo.qooxdoo.org/current/apiviewer/#qx.log.MLogging#printStackTrace > > Best Fabian >> When debugging with Firebug, how do you deal with long stack traces? >> In Firebug 1.0, only the last 10 or so can be accessed (depending on the >> resoution of your screen). >> Call stacks can be very nested in qooxdoo. >> >> I complaint to the author of Firebug long ago, but it hasn´t been solved. >> Any workaround? >> Thanks for sharing any trick. > -- View this message in context: http://www.nabble.com/Long-stack-traces-tf3922256.html#a11134287 Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
