XPConnect duplicates internal JS stack dumping logic, twice

RESOLVED INACTIVE

Status

()

RESOLVED INACTIVE
7 years ago
5 months ago

People

(Reporter: luke, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Maybe more than twice, I don't know.  At the least, I can see XPCJSStackFrame::CreateStack and FormatJSFrame.

In addition to the obvious badness, this is a problem since we'd eventually like to totally remove JSStackFrame from the public interface.  Also, all of this logic is much easer to write inside the JS engine and is already more-or-less present in js_DumpStackFrame.  The only problem is that js_DumpStackFrame prints to stderr whereas the XPConnect uses want the result in different forms, but this should be solvable by simple refactoring.

Comment 1

5 months ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.