Closed
Bug 1206389
Opened 10 years ago
Closed 7 years ago
Addon Debugger Not Showing Breakpoint Hit
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dshcs2, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [specification][type:bug])
What did you do?
================
This was originally encountered in FF 42.0 (32-bit) and reproduced in FF 42.0a2 (Dev Ed 64-bit). A simple bootstrap extension was created and installed. The bootstrap entry points were simple console.log. The extension works as expected with messages logged in install, startup, shutdown and uninstall. The addon debugger is started by clicking on the “Debug” button for the extension, the connection is authorized and the Debugger window opens with Console, Debugger and Scratchpad tabs. A breakpoint is set in the “startup” function and the extension disabled/enabled from the “Add-ons” window. The expected message is logged as the extension is shutdown. When the extension is enabled, the debugger stops the script, but there is no green arrow hit indicator on the javascript code in the Debugger pane. The debugger show the script is stopped. If you click on the “Console” tab, the “Debugger” tab shows a green hit arrow, but if you go back to the Debugger tab, there is no hit indicator. There are also no variables shown while the script is stopped (I added some just to test that) and variables that were created before the breakpoint cannot be watched.
What happened?
==============
When the extension is enabled, the debugger stops the script, but there is no green arrow hit indicator on the javascript code in the Debugger pane. The debugger show the script is stopped. If you click on the “Console” tab, the “Debugger” tab shows a green hit arrow, but if you go back to the Debugger tab, there is no hit indicator. There are also no variables shown while the script is stopped (I added some just to test that) and variables that were created before the breakpoint cannot be watched.
What should have happened?
==========================
A green hit indicator should have been displayed on the line of code containing the breakpoint that was hit.
Is there anything else we should know?
======================================
RDF contents
<?xml version="1.0"?>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">
<Description about="urn:mozilla:install-manifest">
<em:id>ClickIntercept@myextension.com</em:id>
<em:name>ClickIntercept Extension</em:name>
<em:description>ClickIntercept Description</em:description>
<em:version>0.1</em:version>
<em:creator>DLC</em:creator>
<em:homepageURL>http://myextension.com</em:homepageURL>
<em:updateURL>https://myextension.com/update</em:updateURL>
<em:type>2</em:type>
<em:multiprocessCompatible>true</em:multiprocessCompatible>
<em:bootstrap>true</em:bootstrap>
<!-- Mozilla Firefox -->
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>30.0</em:minVersion>
<em:maxVersion>44.0</em:maxVersion>
</Description>
</em:targetApplication>
</Description>
</RDF>
Updated•10 years ago
|
Component: General → Developer Tools: Debugger
Product: Mozilla Developer Network → Firefox
Updated•8 years ago
|
Product: Firefox → DevTools
Comment 1•7 years ago
|
||
closing as i believe this relates to the legacy bootstrapped addons. Feel free to re-open if this is not the case.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•