Closed Bug 1565578 Opened 6 years ago Closed 6 years ago

'Step in' exits function

Categories

(DevTools :: Debugger, defect, P1)

67 Branch
defect

Tracking

(firefox-esr60 unaffected, firefox-esr68 wontfix, firefox68 wontfix, firefox69 wontfix, firefox70 fixed)

RESOLVED FIXED
Firefox 70
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- fixed

People

(Reporter: Oriol, Assigned: jlast)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [debugger-mvp])

Attachments

(1 file)

  1. Run this code in the console:
    (function(){
      debugger;
      var a = 1;
      var b = 2;
    })();
    
  2. The debugger pauses at debugger;
  3. Step in

Expected: the debugger pauses at var a = 1;
Result: the debugger pauses at })();

Regression window: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b7ae64d5ac774ce9054e8aa3431ecd992594447b&tochange=0ab76cc4232f56936e1a2609823f0c13272ca449

Flags: needinfo?(poirot.alex)
Regressed by: 1523943
Blocks: dbg-70
Priority: -- → P1
Whiteboard: [debugger-mvp]
Assignee: nobody → jlaster
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70

Is this something we should consider uplifting to Beta for Fx69 or can it ride to release with Fx70?

Flags: needinfo?(jlaster)
Flags: in-testsuite+

I don't think it is important enough.

Flags: needinfo?(jlaster)
Regressions: 1571380
Flags: needinfo?(poirot.alex)

(In reply to Jason Laster [:jlast] from comment #5)

I don't think it is important enough.

Is it? It sounds like a very disturbing breakage to have around breakpoints. One which can make developer quite unhappy regarding our tools quality. I thought that breakpoint correctness was a top level goal for the debugger?
Now, it is very surprising for me to see how long it took to get a report about this breakage, which may be the one reason to not consider this as important.

Harald and I discussed this last week and it is a difficult call.

This bug makes it impossible to step through console evaluated code. On the other hand, this fix is somewhat risky and could affect much more common use cases.

Given that, I am hesitant to uplift the changeset and have a small window to address any unforseen issues before they go out to release.

A(In reply to Jason Laster [:jlast] from comment #7)

This bug makes it impossible to step through console evaluated code. On the other hand, this fix is somewhat risky and could affect much more common use cases.

Ah sorry. I was mislead by the bug title. I missed that it was only when the code we step through is from a console evaluation. I thought it was more generic than that.

I now better understand your call! It sounds sensible to me as well.

Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: