Updates:
Owner: [email protected]
Comment #1 on issue 25172 by [email protected]: Debugger fails to report
what the error is that caused it to stop
http://code.google.com/p/chromium/issues/detail?id=25172
Chrome ToT there is no indication of which exception caused a break on
exception a
break in the source code is displayed but to get the message in the console
continue
is needed. When running the tests associated with this bug on Chrome it
just stops
in the JavaScript debugger with a break point indication and you need to
continue to
get the exception in the console. This is actually the same on Safari 4 if
both
JavaScript debugging and break on exception are enabled. On Chrome
JavaScript
debugging and break on exception are enabled by default which is not the
case on
Safari.
On Chrome 3 the dev tools have the in-source indication of which exception
happened.
Information on that this is a break on unhandled exception and the actual
exception
is needed in some form.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
