Closed
Bug 481008
Opened 16 years ago
Closed 3 years ago
js shell should print a stack trace on uncaught exceptions
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jorendorff, Unassigned)
References
Details
(Whiteboard: [gaming-tools])
Bonus points for including source lines, a la Python.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•9 years ago
|
Whiteboard: [gaming-tools]
Updated•9 years ago
|
Priority: -- → P2
Comment 1•9 years ago
|
||
stack trace is added in bug 1133191.
source lines printing is not.
See Also: → 1133191
Comment 2•9 years ago
|
||
Unsure what the best way to associate SavedFrames and ScriptSources would be. Probably don't want to strongly hold ScriptSources alive from SavedFrame.
Comment 3•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 4•3 years ago
|
||
This works now:
js> function foo() { throw "hi"; } function bar() { foo(); }; function baz() {bar(); }
js> baz()
typein:1:18 uncaught exception: hi
Stack:
foo@typein:1:18
bar@typein:1:49
baz@typein:1:75
@typein:2:1
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•