Closed Bug 449467 Opened 13 years ago Closed 10 years ago

Expose jsdIScript byte codes


(Core :: JavaScript Engine, enhancement)

Windows XP
Not set





(Reporter: johnjbarton, Unassigned)



As far as I know there is no way to print the byte code or other representation of the compiled Javascript matching a jsdIScript. Mostly this is a good thing, but some Firebug bugs are stuck because I can't tell what the method really should be doing.  For example,
is an example of a function that Firebug causes wrong execution when it single steps through the function. Why? I really don't have a way to work on this.  If I could look at the byte codes and the pc while single stepping may be I could get some hints.
Component: General → JavaScript Debugger
Product: Firefox → Other Applications
Version: unspecified → Trunk
QA Contact: general → venkman
Moving to JSD, but it might be JS Engine. Talk to people who know more than me.
Component: Venkman JS Debugger → JavaScript Debugging APIs
Product: Other Applications → Core
QA Contact: venkman → jsd
Summary: [jsd] Expose jsdIScript byte codes → Expose jsdIScript byte codes
John: you can use windbg, to examine the bytecode.

While it's theoretically possible to expose this, I'm not in a hurry to do so. Especially given that the bytecode is not guaranteed to mean anything and given that I don't know how JIT affects this.
Severity: normal → enhancement
Apparently there is a program that gives the byte codes, see for example
See also Bug 533874 -  Implement ast_uneval()/eval_to_ast()
See Also: → 533874
Component: JavaScript Debugging/Profiling APIs → JavaScript Engine
I'm not aware of any current demand for a feature like this.
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.