510138 - Error console handles nsIExceptions and nsIXPCExceptions horribly.

Status: RESOLVED WONTFIX

(Toolkit Graveyard :: Error Console, defect)

Description

[Nochum Sossonko [:Natch]]

Make it better!

Comment 1

[Nochum Sossonko [:Natch]]

Simon, would you be ok with parsing the nsIScriptError message to make a more useful entry as an interim solution?

Currently nsIXPCExceptions are serialized into a single string when they go from exception to error, that string has valuable information that can be better handled by the error console.

The best solution would be to fix that serialization, I'll file a bug for that too.

Comment 2

[Simon Bünzli]

(In reply to comment #1)
Sure. You should even be able to reuse parseUncaughtException from Console²'s http://www.mozdev.org/source/browse/console2/src/console2/chrome/content/console2/console2.xml?rev=1.8

Comment 3

[Philip Chee]

zeniko: Every time I look at your monster regexp, I run screaming away.

Comment 4

[Nochum Sossonko [:Natch]]

Is it really necessary to test the message string to figure out if it was an nsIXPCException? What about the exceptionFlag on nsIScriptError, does that not tell you that it was an exception as opposed to just an ordinary error?

(In reply to comment #3)
Lol, that is a monstrous RegExp, kudos Simon :)

Comment 5

[Rob Campbell [:rc] (:robcee)]

terrifying!

Comment 6

[Nochum Sossonko [:Natch]]

->default

Comment 7

[Brian Grinstead [:bgrins]]

The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed.  If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.

Comment 8

[Zack Weinberg (:zwol)]

I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console.

If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid.  Do not push that work onto the bug reporters.

(It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify.  But that is the ONLY situation where it is okay.)

(I'm going to have to do this in two steps because of the way the "change several bugs at once" form works.  Apologies for the extra bugspam.)

Comment 9

[Brian Grinstead [:bgrins]]

The Error Console feature was removed entirely from the tree in Bug 1278368 and the bugzilla component is now being removed. We’ve migrated bugs that seem to also affect the Browser Console into the devtools component, please move this over if it was missed.