JSStackFrame Evisceration: Difference between revisions

JSStackFrame Evisceration (view source)

262 bytes removed , 25 August 2010

Confirmed users

367

edits

@@ Line 13: / Line 13: @@
 |-
 | [https://bugzilla.mozilla.org/show_bug.cgi?id=539144 argc/argv/fun/script/thisv]
-| 1.5
+| 3
 | lw
-| Requires CallSegment (CallStack) changes, educate decompiler
+| Requires StackSegment [https://bugzilla.mozilla.org/show_bug.cgi?id=579183 changes].
 |-
 | ncode
@@ Line 27: / Line 27: @@
 | Remove display optimization for great justice!
 |-
-| hookData
+| XhookData
-| 1
+| .1
 |
-| Once we are inlining call paths, we can know statically, based on the compartment-wide 'debug mode' flag, whether we can just ignore cx->debugHooks->callHook and leave hookData uninitialized.  To actually remove the JSStackFrame member (without having the size depend on whether we are in debug mode or not), we can maintain a debugHook stack on the side.
+| Lazily initialize using JSStackFrame::flags.  Included in bug 539144.
 |-
 | [https://bugzilla.mozilla.org/show_bug.cgi?id=546848 annotation]