CODEWITHSUNDEEP
c#visual-studiodebuggingbreakpoints
Wil
Wil

Reputation: 10604

Visual Studio is missing/moving my breakpoints

The problem is that when I place a breakpoint and debug/run, the breakpoint moves by itself.

Before/whilst coding:

enter image description here

After clicking run/breakpoint hit:

enter image description here

Breakpoints typically work ok for me, but it seems that they sometimes randomly play up. I first had this ages ago with a VB project, and in the end, I bypassed the problem by removing the breakpoint and adding it somewhere else where it was still useful.

Whilst I could probably do the same again, and this is only the second time it has happened (that I remember), I don't really want to have to and would like to know what is actually wrong.

I have read through many similar questions here, but I cannot see an exact match and the answers do not help. I have tried - building, rebuilding, closing/reopening and cleaning.

I only provided a picture of the bit of code where it occurs, if you need anything else, please let me know.

Upvotes: 21

Views: 11113

Answers (5)

T.Todua
T.Todua

Reputation: 56497

for Visual Studio Code users, it might be related to TS/NODE :

Upvotes: 0

amonroejj
amonroejj

Reputation: 633

You can get this if the breakpoint is AFTER a return statement. Visual Studio will bounce the breakpoint to the closing brace (or "End Function" for VB.NET) because return is jumping out of the function.

Upvotes: 0

Mike Burger
Mike Burger

Reputation: 341

Also check to see if you had set the breakpoints in one mode (Debug) but are now in a different mode (like Release). This caused me some momentary angst.

Upvotes: 12

Sebastian Hoggard
Sebastian Hoggard

Reputation: 31

I got this problem after Windows had inexplicably added 6 months to the current system date (and 1 hour to the time). I didn't correct this right away, so builds made before the correction looked more recent to Visual. This lead to running the wrong (older) build when debugging.

Since I couldn't find a "Clean Solution/Project" option, I had to manually delete all .pdb files in the solution. The problem was instantly fixed. I just hope there aren't any more files I might need to delete (I'm new to Visual and don't know much about how it works behind the scenes).

Upvotes: 3

user541686
user541686

Reputation: 210643

It's because the debugger isn't able to break at that point. For example, the debugger can't break on auto-implemented properties, or at the header of a method; instead, it breaks at the first line of the method.

Upvotes: 14

Related Questions