Closed
Bug 1092270
Opened 11 years ago
Closed 8 years ago
Make jpm test --debug work, and only load main after the debugger has loaded
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: evold, Unassigned)
References
(Blocks 1 open bug)
Details
Moving https://github.com/mozilla/addon-sdk/blob/master/lib/sdk/addon/runner.js#L160-L162 just before https://github.com/mozilla/addon-sdk/blob/master/lib/sdk/addon/runner.js#L145 making sure to call `main(options.loader, options.main);` only after the debugger is setup should resolve this issue.
Basically we need to load the debugger before loading the main script for an add-on, in order to catch `debugger;` statements
| Reporter | ||
Updated•11 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Comment 1•11 years ago
|
||
I fear it won't be so easy. The Browser Toolbox looks to be initiated asynchronously.
https://hg.mozilla.org/mozilla-central/file/ad6298e44579/browser/devtools/framework/ToolboxProcess.jsm#l203
What would be great is a callback from the toolbox (a RDP message or so) telling that it is wholly loaded (with the Debugger, etc.).
Florent
Updated•11 years ago
|
Priority: -- → P2
| Reporter | ||
Comment 2•11 years ago
|
||
Note: Need to make a related devtools bug here.
| Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(evold)
Comment 4•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•