Comment #4 on issue 1722 by [email protected]: Native DOMExceptions don't have stack traces
http://code.google.com/p/v8/issues/detail?id=1722
The issue is, let's say Gmail (Closure) or AdWords (GWT) gets a random DOMException thrown in production. When we intercept this exception as it bubbles up, we need the e.stack property so that we can log to the server what caused it and where. Right now, we get no information. We can't use window.onerror because that only works if the exception is never caught or rethrown. And we can't put try/catch blocks around every callsite that makes DOM calls as it is massively inefficient.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
