I've been using the free Microsoft debugger called Visual Web Developer 2008
for a while now. It's great: when something bad happens you get a nice stack
to look at and an immediate window where you can evaluate expressions. In
other words, a real debugger, even in IE.
However, since I upgraded to qooxdoo 1.0, I'm finding that many stack traces
are bogus. If I refer to a nonexistent property -- due to a typo for example
-- then I get an alert box in the debugger saying something sensible like
"object does not support this property or method", but when I break and look
at the stack trace, it's always the same: it starts with a "mouseup" event
handler and ends up in some mystery function with these locals:
callback: {...}
finallyCode: {...}
self: {Class qx.ui.core.queue.Manager}
e: {Object does not support this property or method}
and the debugger shows me some totally unrelated lines of code in the source
view.
This happens with both the 2008 and the 2010 Beta 2 versions.
QooxDoo gods, any clues what's hijacking my stack when exceptions occur?
This makes debugging typos take about 100 times longer.
Dave
--
View this message in context:
http://n2.nabble.com/QooxDoo-1-0-breaks-stack-traces-in-Visual-Web-Developer-tp4514657p4514657.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
