Menu
While debugging a combined c++ c# project (c# loading a c++ dll) I'm sometimes getting this small blue dot beneath the currently hit breakpoint: 
What does that dot want to tell me?
336
To disable a breakpoint without deleting it, hover over or right-click it, and select Disable breakpoint. Disabled breakpoints appear as empty dots in the left margin or the Breakpoints window. To re-enable a breakpoint, hover over or right-click it, and select Enable breakpoint.
Breakpoints are the most basic and essential feature of reliable debugging. A breakpoint indicates where Visual Studio should suspend your running code so you can take a look at the values of variables, or the behavior of memory, or whether or not a branch of code is getting run.
Breakpoints is a feature provided by the debugger in Microsoft Visual Studio that allows breaking execution of code at runtime when debugging applications. When you click on the side (in the margin) of a line of code in Visual Studio it sets a break point in your code as displayed in the image above.
If a source file has changed and the source no longer matches the code you're debugging, the debugger won't set breakpoints in the code by default. Normally, this problem happens when a source file is changed, but the source code wasn't rebuilt. To fix this issue, rebuild the project.
If you app is multithreaded and if hovering over break point gives you message is like "The process or thread has changed since the last step" it means that this break point is applied to more then one thread, not just thread creator. After you press F5 another threads will run and they will hit your break point which can confuse you. In order to give you some kind of warning visual studio give you blue dot beneath. So sometimes it can be useful to freeze other threads in order to debug method.
194
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
