Using the Chrome debugger, I could get closer to the source of the error, and
I could display the stack trace of the original error object that gets
passed to qx.core.Object.prototype.error():
"TypeError: Cannot read property 'load' of undefined
at qx.Bootstrap.define.members.require (https://...)
at qx.Class.define.members.require (https://...)
at qx.Class.define.statics.require (...)
at loadScript (...)
at null.<anonymous> (...)
at ...
at Object.qx.Bootstrap.define.statics.delay (....)
at null.<anonymous> (...)
at ...
at handleRequestFinished (...)"
This is much better and much more informative than the stack trace displayed
by qx.core.Object.prototype.error(). Is there any chance that this method
could be rewritten to display this stack trace instead of the completely
unusable stack trace that is now displayed in the case of async errors?
Should I open a bug report?
Thank you.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/qooxdoo-Stacktrace-problems-tp7586130p7586136.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
