Bug 42560 – Web Inspector: show stack trace for uncaught exceptions

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Yury Semikhatsky]

If you throw an exception in your javascript, the web inspector console just 
prints out the description of the extension and doesn't give the stack trace.  
This is particularly unhelpful if the exception is being thrown in a library 
many levels removed from the source of the error in your code.

[Yury Semikhatsky]

Created attachment 61943 [details]
Patch

[Pavel Feldman]

Comment on attachment 61943 [details]
Patch

It looks correct, however, I think we've reached the critical mass of mess in the code. Can we refactor it to make prettier?

My concern is that ScriptCallStack means two different things in different call paths: 
(1) it is used as a top frame + script state for console.log/dir/etc
(2) it is used as a stack container with no access to top frame arguments in regular console messages

[Yury Semikhatsky]

(In reply to comment #2)
> (From update of attachment 61943 [details])
> It looks correct, however, I think we've reached the critical mass of mess in the code. Can we refactor it to make prettier?
> 
> My concern is that ScriptCallStack means two different things in different call paths: 
> (1) it is used as a top frame + script state for console.log/dir/etc
> (2) it is used as a stack container with no access to top frame arguments in regular console messages

Filed a bug for this: https://bugs.webkit.org/show_bug.cgi?id=42570

[Yury Semikhatsky]

Comment on attachment 61943 [details]
Patch

Clearing flags on attachment: 61943

Committed r63662: <http://trac.webkit.org/changeset/63662>

[Yury Semikhatsky]

All reviewed patches have been landed.  Closing bug.