4.3.x MonoDevelop Breakpoints not working

Unity Engine
1

List of bugs:

Windows 7

Breakpoints not working
http://puu.sh/5DHbF.png
Frequency: Always
Fix: Nothing works.
Tried: Waiting. Starting and closing debug many times. Restart. Reinstalling. Completely removal and install. Manual attaching. Turning debugging off/on.

THIS IS DRIVING ME NUTS, I BASICALLY CAN’T WORK ANYMORE AS A PROGRAMMER BECAUSE THE DAMN THING DON’T WORK!!!

Monodevelop won’t open
Frequency: Very often
Fix: Go to Task Manager and kill monodevelop process, try again.

Monodevelop squared text
http://puu.sh/5D44Z
Frequency: Often
Fix: Go to Task Manager and kill monodevelop process, try again.

Everything sucks and I want to kill everyone
Frequency: Always
Fix: FIX MONODEVELOP BREAKPOINTS

1 Like
2

No answer yet, still can’t work.

3

Installed UnityVS, uninstalled, breakpoints are now working in monodevelop (???)

Edit: Step Over, Into and Out not working, all of them jump to the next breakpoint.

4

I have the same problem, and I seem to finally have a working debugger again. Hopefully it’s not too soon to tell.

This is what seems to have worked to get the MonoDevelop debugger working [haven’t tried UnityVS at all, so can’t comment on that]

From Unity > Assets > Reimport All

Good luck.

5

I had this too, sometimes they work sometimes they don’t who the hell knows why.

6

Actually I tried that to no avail before, and I had the same problem again after and it vanished in a few minutes…

Seems totally random about everything, when it happens, how much it lasts…

7

Yup, I keep having all the issues OP described. This is ridiculous.

8

Same here, breakpoints sometimes work, and sometimes they don’t. Completely random, completely frustrating!

When Mono is not attached attached to Unity the breakpoint marker is a solid dot, then soon as I attach it goes to the empty circle…and doesn’t work.

9

Having the exact same issues described. Monodevelop breakpoints seem to be completely inoperative. They appear as empty circles now when I place them, instead of a solid dot as before.

Monodevelop also frequently won’t open, have to kill the process as described in OP.

10

Exact same issues here. Restarting Unity and MonoDevelop sometimes works for me and sometimes doesn’t. Sometimes breakpoints that were present when you started debugging work but new ones don’t.

In addition to the issues above I also get the one where the tabs can no longer be clicked to change the active document or close a document. Keyboard shortcuts still work but the tab UI becomes unresponsive.

Having to restart MonoDevelop/Unity every 20 minutes or so to keep basic functionality.

Unity 4.3.2f1
MonoDevelop 4.0.1
Win 7

11

So I had this issue just a few moments ago, here’s what I did to fix it:

Close Unity
Close Monodevelop (and kill any lingering processes via TaskManager)
Delete LibraryFolder
Delete MonoDevelop Cache (for Win7 it’s located at: C:\Users<YOUR USERNAME>\AppData\Local\MonoDevelop-Unity-4.0 )
Restart PC

The most important part is probably deleting the cache though.

Also, before this issue occured, I tried to attach the debugger ,while the game was running. It couldn’t move a .dll and after that,breakpoints got ignored (and their red dots where desaturated as soon as I attached it to the UnityEditor process, game running or not).

12

Thank you for so much for this. I just couldn’t get debugger working on my Mac. Unity3D would just hang if I tried to debug with MonoDevelop attached. After deleting ~/Library/Cache/MonoDevelop-Unity-4.0 everything seems to be working again. Thx again!

13

Maybe spoke too soon. Now it is beach ball of death again when trying to debug. I’ll try to remove the Cache again to see if that makes a difference.

14

Removing Cache files didn’t make a difference this time. Maybe I should do some additional steps, like restarting the computer…

I really hate the thing that the debugger doesn’t work, hopefully it will be fixed soon.

15

Hi,
I have the same problem since installing Unity 4.3, never had it before. The problem did not appear immediately, it worked for a few days then the breakpoints stopped working. I am not aware of any “special” manupulation that could have caused the problem…

I did the Delete LibraryFolder / Delete MonoDevelop Cache / Restart PC manipulation and it works again, hopefully it won’t happen too often…

16

Hi there,

  • First of all, can I ask, which version of Unity are you currently using?

  • Does this happen on one particular project, or can you create a project from scratch (e.g. with one C# script) and find that you get this problem?

  • Do you have another PC which you can try running the same version of Unity on to see if the problem is limited to just one PC?

  • Did this start happening after a certain event (e.g. upgrade of Unity or and upgrade of some other software on your PC)?

Dave

17

Hello again,
I kinda found what causes the problem in my situation.
Basically after one hour or so I get a “moving file failed” error
1524772--87568--$moving file failed.png
(same problem as in this thread:
Moving file failed - Questions & Answers - Unity Discussions )
if I click on “retry” the dialog pops again immediatly, if I click on “force quit” I can save the situation (but I have to restart Unity), and if I click on “Cancel” things keep working but the Unity/Monodevelop link gets broken somehow and the breackpoints won’t work anymore.
I tried to disable all the programs which could access the files (MacAfee real time analysis, iDrive backup), to deactivate file indexation, to launch monodevelop and Unity as Administrator, but I still get the Moving File error.

As a side note I have a warning at launch since I upgraded to Unity 4.3.4f1: “Couldn’t set project path to c:\Unity Projects\Solum\Assets”, it does not stop things from working, so I don’t know if there is a relation with the other problems or not.

18

Hi Dave, to answer your questions:

  • I use Unity 4.3.4f1, I did not have this problem before. I was able to work for a day or so without this problem, but now I get it very regularly.
  • I can’t test right now if the problem arises on another project/machine since i’m in a rush and the problem appears randomly after an hour or so. I will try to test that when I have more time…
  • no recent software update, excepted PlayClaw5 (video capture)
19

So did the problem start to happen with 4.3.4, and not happen with 4.3.3 ?
What happens if you use 4.3.3 ?
And did you say you think it is connected to the “moving file failed” problem?

20

I upgraded directly from one of the last Unity 3.x versions to 4.3.4, so i wouldn’t know if it would have done the same with 4.3.3.
And in my case (don’t know about the topic creator), it’s definitely bound to the “moving file failed” problem, I have been able to reproduce it a few times now:

  1. I use Unity for a while…
  2. the moving file failed dialog appears, I press cancel
  3. the breackpoints don’t work anymore, even when restarting everything/rebooting
  4. I delete the LibraryFolder and the MonoDevelop Cache, reboot…
  5. Goto 1)