Closed Bug 1525685 Opened 5 years ago Closed 5 years ago

Remove breakpoint sliding code

Categories

(DevTools :: Debugger, enhancement)

enhancement
Not set
normal

Tracking

(firefox67 fixed)

RESOLVED FIXED
Firefox 67
Tracking Status
firefox67 --- fixed

People

(Reporter: bhackett1024, Assigned: bhackett1024)

References

Details

Attachments

(2 files)

Breakpoint sliding is not needed anymore now that the client knows where it is able to set breakpoints. It helps to get rid of this in preparation for removing breakpoint actors, as it is tricky to support breakpoint sliding when there is no actor for the breakpoint.

Attached patch server changesSplinter Review

Changes to the server and SourceClient. I'll make a PR for the debugger.html changes separately.

Attachment #9041892 - Flags: review?(lsmyth)
Comment on attachment 9041892 [details] [diff] [review]
server changes

Review of attachment 9041892 [details] [diff] [review]:
-----------------------------------------------------------------

My only hesitation on this is wondering if we should wait for column breakpoints to be on by default. That said, it's probably fine. There are definitely cases when column breakpoints are disabled and this branch still runs if I remember right.

Are all the tests passing on this? I'm surprised none needed changes.

::: devtools/server/actors/source.js
@@ -748,5 @@
> -   *
> -   * @returns A Boolean that is true if the BreakpointActor was set as a
> -   *          breakpoint handler on at least one script, and false otherwise.
> -   */
> -  _setBreakpointAtGeneratedLocation: function(actor, generatedLocation) {

This is used in the thread actor as well.

(In reply to Logan Smyth [:loganfsmyth] from comment #2)

Comment on attachment 9041892 [details] [diff] [review]
server changes

Review of attachment 9041892 [details] [diff] [review]:

My only hesitation on this is wondering if we should wait for column
breakpoints to be on by default. That said, it's probably fine. There are
definitely cases when column breakpoints are disabled and this branch still
runs if I remember right.

This change blocks bug 1524374, which is necessary for correct breakpoint behavior with workers. If we keep the sliding code around then I'll have to find some way of implementing it with the changes in bug 1524374, which isn't a good use of time if we don't actually need sliding anywhere.

Are all the tests passing on this? I'm surprised none needed changes.

I haven't run mochitests but I did have to update some unit tests in the client (PR #7895). I'll post another patch if any test changes are needed.

::: devtools/server/actors/source.js
@@ -748,5 @@

    • @returns A Boolean that is true if the BreakpointActor was set as a
    •      breakpoint handler on at least one script, and false otherwise.
      
  • */
  • _setBreakpointAtGeneratedLocation: function(actor, generatedLocation) {

This is used in the thread actor as well.

Oops, I'll update the patch. I have a WIP for bug 1524374 which removes the call in the thread actor, which can be done without using private methods of the source actor I think.

Attachment #9041890 - Flags: review+

_setBreakpointAtGeneratedLocation

This might need to be kept, but this looks good otherwise as long as tests are passing.

(In reply to Brian Hackett (:bhackett) from comment #3)

This change blocks bug 1524374, which is necessary for correct breakpoint behavior with workers. If we keep the sliding code around then I'll have to find some way of implementing it with the changes in bug 1524374, which isn't a good use of time if we don't actually need sliding anywhere.

Fair enough. Go for it, we can always reevaluate if it causes issues after landing.

Severity: normal → enhancement
Pushed by bhackett@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/95bfbc0f513d
Remove server side breakpoint sliding code, r=jlast.
Pushed by bhackett@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/dcb8d820d2c1
Remove server side breakpoint sliding code, r=jlast.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 67
Flags: needinfo?(bhackett1024)
Attachment #9041892 - Flags: review?(lsmyth)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: