JS Error stacktrace in nightlies differs from previous versions

RESOLVED WONTFIX

Status

()

Core
JavaScript Engine
RESOLVED WONTFIX
8 years ago
8 years ago

People

(Reporter: dchan, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
Created attachment 482750 [details]
test case

The latest nightlies appear to be missing the top most stack frame when an exception is thrown.

STR
1. Open test.html, it will open an alert with the stack

Firefox 4.0b6 / 3.6.9 displays
Error("foo")@:0
@file:///Users/dchan/test.html:5

Firefox 4.0b8pre displays
@file:///Users/dchan/test.html:5

Updated

8 years ago
Assignee: general → xpconnect

Comment 1

8 years ago
This also bit Myk with iterators.
Aren't both of these bugs fallout from slow native removal? (That is, aren't they JS engine "bugs?").

Comment 3

8 years ago
Ah, right. Good point!

Comment 4

8 years ago
This change is indeed from slow-native removal: the error constructor no longer pushes a stack frame.  This change in behavior was discussed ahead of time and considered acceptable.  If there is a good reason, we could add a non-frame entry corresponding to the arguments of the error constructor.

Updated

8 years ago
Assignee: xpconnect → general
(In reply to comment #1)
> This also bit Myk with iterators.

Note: per my recent m.d.t.js-engine post <http://groups.google.com/group/mozilla.dev.tech.js-engine/browse_thread/thread/c1d4b5bf54e47bb5#c193c2c1c4851e8b>, over in bug 597004 I implemented the workaround suggested by Donny Viszneki <http://groups.google.com/group/mozilla.dev.tech.js-engine/browse_thread/thread/c1d4b5bf54e47bb5#77fbe60381c652aa> for the custom iterators in the Jetpack SDK.

Comment 6

8 years ago
Great
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.