Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 7240 by [email protected]: Exception object In Chrome Doesn't
Provide Useful Debugging Information
http://code.google.com/p/chromium/issues/detail?id=7240
Every browser has it's own implementation of the exception object that is
passed to a catch() statement which is annoying enough as it is, but Google
Chrome's exception object is way below par compared to other browsers. The
only property of the exception object that is implemented in all other
browsers, "message" seems to always be an empty string in Chrome, and the
browser provides no stack trace, no filename, no line number, no line
position and no error number. Additionally, it uses the property name
"arguments" which is a reserved word and makes JSLint unhappy.
Why is this object so lacking in detail? Surely it's easy to provide at
least the line number and filename where the error occurred and a simple
"message" property? The lack of this information makes Chrome far less
attractive for a developer looking to debug their JavaScript code.
Chrome Version : 1.0.154.46
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 3: OK
Firefox 3: OK
IE 7: OK
What steps will reproduce the problem?
1. Run the following script in Chrome:
try {
splooge()
} catch (e) {
for (p in e) {
document.write('e.' + p + '=' + e[p] + '<br />');
}
}
What is the expected result?
A decent amount of information about the error encountered
What happens instead?
A feeble amount of information about the error encountered that isn't very
helpful either for debugging or diagnosis.
Please provide any additional information below. Attach a screenshot if
possible.
--
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
-~----------~----~----~----~------~----~------~--~---
