GNOME Bugzilla – Bug 695718
jsapi-util: Cut down on error reporting
Last modified: 2013-05-07 15:39:53 UTC
This is a massive improvement to how we present JS errors, I think.
Created attachment 238715 [details] [review] jsapi-util: Cut down on error reporting The message, filename and line number are already reported as part of the debug message and stack, so don't bother emitting then. Instead, just show the error message and stack. At the same time, remove the "Exception was: " prefix.
Review of attachment 238715 [details] [review]: This patch loses the exception message from logError(). Also, the indentation is still awkward in log messages, as the first line of stack is displayed differently.
(In reply to comment #2) > Review of attachment 238715 [details] [review]: > > This patch loses the exception message from logError(). Hm. I'm not sure what correct logging output would look like. Should we just do user message, exception message, stack? (In reply to comment #2) > Also, the indentation is still awkward in log messages, as the first line of > stack is displayed differently. Yeah, I'm not sure how we want to solve that, though. At the very least, we can take out fileName and lineNumber without losing much.
Created attachment 238724 [details] [review] jsapi-util: Don't emit the fileName/lineNumber It's part of the stack, so it's not really useful.
Created attachment 238725 [details] [review] jsapi-util: Remove the "Exception was:" prefix It's just noise, and doesn't really add anything.
Review of attachment 238724 [details] [review]: Ops, this slipped out of sight. They both look fine, although it's you choice if you target 1.30.1 or 1.31.1
Review of attachment 238725 [details] [review]: Yes.
Hey, are you going to merge these ones? I started to work on 690984 again, which kind of supersedes this.
Hm. Seems I didn't notice they got ACN'd at some point. Just merge your patches.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 690984 ***