Closed Bug 563000 (JaegerDebug) Opened 14 years ago Closed 11 years ago

JM: Debugging support


(Core :: JavaScript Engine, defect)

Not set





(Reporter: dmandelin, Unassigned)




(1 file)

JM needs to support debuggers. Although it would be possible to do this by copying what TM does, and just not run in the JIT when the debugger is active, we have decided that is not a good user experience.

Instead, when a script needs to be debugged, we will recompile it in a way that allows the debugger to do everything it needs to do. We might compile it once, or maybe once for each breakpoint that is set--compilation is fast, so we have freedom. Details must be worked out later.

We also need to coordinate this with the new debug API project.
Alias: JaegerDebug
Depends on: 570650
Depends on: 578153
Depends on: 578157
See Also: → 578159
Depends on: 580428
Blocks: 580428
No longer depends on: 580428
No longer blocks: 580428
Depends on: 582409
Depends on: 582419
Depends on: 578154
Depends on: 586104
Depends on: 586105
Depends on: 586107
Forces debug mode to true so firebug can be tested.
Depends on: 594054
Depends on: 595243
Would it be possible to provide two modes for debuggers? Could we have a normal JIT-off mode for debugging, but add an option to flick JIT back on temporarily during a JS profiling run (when presumably the user doesn't need to break or step through the code)?

(Otherwise debugger users can't really have confidence in the numbers a profile gives to provide insight into the end user experience when a debugger is not attached, and the numbers can make us look bad when everything's actually fine without the debugger attached.)
Depends on: 599400
Depends on: 601197
Depends on: 602003
Depends on: 609663
Depends on: 612717
Depends on: 613482
Depends on: 615277
Depends on: 617870
Blocks: compartments
No longer blocks: JaegerBrowser
Depends on: 619641
Baseline Compiler landed with debugging support.  JM debugging support is probably not in the cards.
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.