Menu
I am writing code in Visual Studio 2017, using C# for Unity.
Sometimes, when I add a breakpoint in some places, it is a hollow circle 
, opposed to the normal circle 
. When this happens, the breakpoint doesn't hit.
If I try and place a breakpoint on an empty line or method signature, I get a hollow breakpoint. But I will also get them on valid, debuggable lines of code. I can debug the hollow ones by finding a valid breakpoint above it, and stepping down.
The breakpoints are not disabled:
Why are my breakpoints hollow sometimes? What does it mean? How can I stop it?
991
To set a breakpoint in source code: Click in the far left margin next to a line of code. You can also select the line and press F9, select Debug > Toggle Breakpoint, or right-click and select Breakpoint > Insert breakpoint. The breakpoint appears as a red dot in the left margin.
This problem occurs because ASP.NET debugging isn't enabled on the application.
New in Xcode 13, if a breakpoint is not resolved to any location by LLDB, Xcode will show you a dashed icon. There is a myriad of reasons why a breakpoint is not resolved but there are some common explanations. If you hover over the unresolved breakpoint icon, we have a tooltip that can help you out.
In my case I saw this message in the Application Output window:
Resolved pending breakpoint for 'Android.Runtime.JNIEnv.RegisterJniNatives(System.IntPtr, System.Int32, System.IntPtr, System.IntPtr, System.Int32)' to [0x0](no debug symbols).
note that at the end of the message it says (no debug symbols). So just simply Cleaning and Rebuilding and also deleting bin and obj folders of all projects worked for me.
84
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
