Breakpoints not working

Question

I checked the monodevelopment breakpoints not working post but it was from a number of years ago and about monodevelopment.

I am using VS 2015 and overnight the breakpoints stopped working. I tried closing everything out an restarting the system - didn't help. Tried different versions of VS - didn't help. Tried using monodevelopment - didn't help.

When I put in a breakpoint in VS attach the C# to unity and run the project the breakpoints are just ignored. Don't know if anything else in debug works since I can't stop the program

Anyone know what is going on and how to fix it? Really hard to do debugging without a debugger!

Answer 1

Answer by andycruce · Sep 27, 2017 at 11:57 AM

I have the same problem. I watched the video but it didn't address the problem. Fro some reason something changes in the the VS-Unity connection and instead of a red dot for the breakpoint I get a hollow red/yellow dot. When I highlight it I get the following message:

The breakpoint will not be currently hit. Unable to find corresponding location.

I tried selecting Attach Unity Debugger in the debug dropdown in VS but this didn't work. I have reinstalled Unity and that didn't clear up the problem either. I am using VS 2107.

I've seen other posts describing this problem but no solutions!

Add comment · Share

Answer 2

Answer by liquidbuddha · May 25, 2018 at 08:22 PM

I am also having the same issue. :( VS 7.5.1, Unity 2018.1.0f2. Re-importing all assets seemed to clear up the issue.

Add comment · Show 2 · Share

Alexees · Sep 12, 2018 at 07:57 AM 0

Share

did help me too (Unity 2018.2.6f1 VS 15.8.4)

jamesnw · Oct 02, 2018 at 01:44 AM 0

Share

I'm constantly having the same/similar issue. Seems like only the breakpoints are hit for code in MonoBehaviour class files, but not in utility class files (completely ignored). In fact, I can step through into the utility code files from a behavior, but the breakpoints inside the utility class files are completely ignored. Also, System.Diagnostics.Debugger.Break(); is completely ignored, as is Debug.Break(). I'm not resorting to throwing and catching exceptions in my utility classes in order to debug them, which is getting really annoying. I noticed my code files getting out of sync also, causing code to stop on incorrect lines, or stopping on invalid code frames. It seems like reimporting the script folder within Unity fixes everything - only until I edit the code in VisualStudio and try to launch debugging from VS as well. This setup is not very reliable as my project is growing.

Answer 3

Answer by Flokky_ · Sep 24, 2017 at 10:22 AM

You can try this tutorial: For the MonoDevelop
Or: For the VisualStudio

Add comment · Share

Breakpoints not working

3 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions