Closed Bug 818382 Opened 10 years ago Closed 10 years ago

Support chrome debugging in Firefox for Android

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 22

People

(Reporter: past, Assigned: past)

Details

(Whiteboard: [chrome-debug])

Attachments

(1 file)

As far as the remote debugging protocol is concerned, chrome debugging is mostly a global thread actor that has visibility to all JS running in the application process. We should add such capability to Firefox for Android in order to make debugging mobile add-ons easier, as well as help debugging Firefox itself.
Whiteboard: [chrome-debug]
filter on BLACKEAGLE.
Priority: -- → P3
Assignee: nobody → past
Status: NEW → ASSIGNED
Attached patch Patch v1Splinter Review
Same patch more-or-less as bug 818385. With this patch, when I connect remotely to Fennec and select Main Process form the target list, I now get a working debugger. The script list displays all the scripts loaded in all JavaScript globals (even JNI.jsm - oh, the memories!). I observed the protocol interactions while adding/removing breakpoints, etc. and it seems to work fine, albeit (dog) slow, like chrome debugging on desktop.

Not sure how useful it will prove to be for our mobile developers, since I assume they mostly deal with Java, but I expect add-on developers to love it (probably after we fix our chrome-debugging bugs).
Attachment #716232 - Flags: review?(mark.finkle)
Comment on attachment 716232 [details] [diff] [review]
Patch v1

Nice!
Attachment #716232 - Flags: review?(mark.finkle) → review+
https://hg.mozilla.org/mozilla-central/rev/bcbe8d700ea5
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 22
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.