JP Richardson d6ae874038 emit error object on process.on('uncaughtException') in renderer ... Chromium added the actual `error` object to the 5th parameter in `window.onerror`. This should be emitted as opposed to the `errorMsg` string. Worse yet, since `errorMsg` wasn't an instance of `Error`, any code that assumes this in any `process.on('uncaughtException')` handler would fail. Also, correctly emitting the error provides the stack trace. This is now an HTML5 standard. Sources: - https://html.spec.whatwg.org/multipage/webappapis.html#errorevent - https://mikewest.org/2013/08/debugging-runtime-errors-with-window-onerror - https://code.google.com/p/chromium/issues/detail?id=147127		2015-07-10 14:38:03 -05:00
..
app	Move headers to atom/common	2015-06-19 23:11:53 +08:00
browser	Allow more insecure content when web-security is off	2015-07-10 13:29:46 +08:00
common	clipboard: api to write multiple formats to same writer	2015-07-10 09:20:52 +05:30
renderer	emit error object on process.on('uncaughtException') in renderer	2015-07-10 14:38:03 -05:00
utility	Rename PrintHandler to PrintHandlerWin since only used on Windows.	2015-05-23 19:24:29 +08:00