Closed Bug 481008 Opened 14 years ago Closed 7 months ago

js shell should print a stack trace on uncaught exceptions

Categories

(Core :: JavaScript Engine, defect, P3)

Other Branch
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: jorendorff, Unassigned)

References

Details

(Whiteboard: [gaming-tools])

Bonus points for including source lines, a la Python.
Assignee: general → nobody
Whiteboard: [gaming-tools]
Priority: -- → P2
stack trace is added in bug 1133191.
source lines printing is not.
See Also: → 1133191
Unsure what the best way to associate SavedFrames and ScriptSources would be. Probably don't want to strongly hold ScriptSources alive from SavedFrame.
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

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: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.