Currently calling TC_setBreakpoint returns an error if the debuggee is running. It would be better for clients to make setBreakpoint interrupt the debuggee in such cases, set the breakpoint and resume.
This is still work in progress.
I was stuck making the test work, until I realised that it uncovered a bug in the client request dispatcher. It now no longer confuses unsolicited notifications from the server as responses to active client requests. The unit test catches this, as well as any issues in the basic interrupt-then-breakpoint functionality.
This is ready to land after its dependencies are reviewed.
Priority: -- → P2
Rebased on top of latest changes during super review.
Attachment #582846 - Attachment is obsolete: true
Updated patch metadata.
Attachment #595698 - Attachment description: Working patch v2.1 → [in-fx-team] Working patch v2.1
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 13
You need to log in before you can comment on or make changes to this bug.