Closed
Bug 932043
Opened 11 years ago
Closed 11 years ago
No error message when I break on an uncaught exception
Categories
(DevTools :: Debugger, defect, P2)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: canuckistani, Assigned: fitzgen)
Details
Attachments
(1 file)
To repro: $(function() { var editor = new Codemirror(); // Codemirror must be undefined }); If 'break on uncaught exceptions' is enabled, the debugger will break on the second line: * the error object has no error message * the web console does not yet show the error message Hitting 'Continue' will then allow the error message to appear in the web console. Note: jQuery is used here, and there was no difference whether jQuery was black-boxed or not.
Reporter | ||
Comment 1•11 years ago
|
||
Screenshot of what I'm seeing.
Assignee | ||
Comment 2•11 years ago
|
||
I haven't done full STR, but I get the error message when enabling pause on exceptions and then just typing new SomeUndefinedThing() in the console. Very interesting. Will look into this soon.
Assignee: nobody → nfitzgerald
Priority: -- → P2
Assignee | ||
Comment 3•11 years ago
|
||
Also, it is expected that the web console doesn't have the error yet, because we caught it before it has unwound all the way.
Reporter | ||
Comment 4•11 years ago
|
||
Mystery solved - I had selected the option 'Show only enumerable properties', by de-selecting that the message property appears. I had selected that option because I didn't want to see __proto__ et al in the Object Inspector. We could close this bug, or we could debate the merits of overriding that preference for this particular case. Up to y'all. Aside: in some future state where I have access to a console view in the debugger, it would be great if exceptions were logged as they happen in that UI.
Assignee | ||
Comment 5•11 years ago
|
||
(In reply to Jeff Griffiths (:canuckistani) from comment #4) > Mystery solved - I had selected the option 'Show only enumerable > properties', by de-selecting that the message property appears. I had > selected that option because I didn't want to see __proto__ et al in the > Object Inspector. > > We could close this bug, or we could debate the merits of overriding that > preference for this particular case. Up to y'all. No, we shouldn't be lying to users. > Aside: in some future state where I have access to a console view in the > debugger, it would be great if exceptions were logged as they happen in that > UI. We also want to be able to continue, but return from the frame with some value you provide instead of bubbling the error to the global frame. We wouldn't want to log the error if you chose to return a value from that frame. /me shrugs
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 6•11 years ago
|
||
I do think it makes sense to have a displayString for errors which has the message though.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•