Reputation: 62886
I am using Fiddler v4.4.1.1 beta.
I once activated automatic before the request breakpoint. Now I have disabled it back, but Fiddler continues to break. I do not know what to do.
Observe:
Notice, the breakpoints are disabled and the same tells the status line - there is no breakpoint icon there.
Yet, the breakpoint is still active:
I cannot use Fiddler any more.
I have issued the bpafter, bps, bpv, bpm and bpu commands without any arguments to clear any possible breakpoint. I have never thought I would ever call Fiddler like this, but it continues to break.
Upvotes: 14
Views: 9293
Reputation: 62886
I finally found it.
There is another place where breakpoints are exposed - the filter tab, which I often use, but never knew it controls breakpoints as well:
The confusing part is that I have never touched this option - only used the host filter part. Apparently, setting an auto breakpoint in the rules menu now sets this flag too, silently. But it is not cleared back when I disable the breakpoint, which is a terrible UI experience.
Upvotes: 16
Reputation: 933
It worked for me like a charm.
You can use the QuickExec (ALT+Q) to enable/disable breakpoints using commands like: bpafter, bpv, bpu
Also one of the killer features is the QuickExec command "g" or "go" that resumes all the breakpointed sessions (this one is available in the UI using the "Go" button).
See Fiddler QuickExec documentation for more info.
Upvotes: 2