4.3.x MonoDevelop Breakpoints not working

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

 

No answer yet, still can't work.

 

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.

 

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.

 

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

 

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...

 

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

 

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.

 

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.

 

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

 

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).

 

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!

 

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.

 

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.

 

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...

 

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

(same problem as in this thread:
http://answers.unity3d.com/questions/137599/moving-file-failed.html )
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.

 

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)

 

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)

 

All the same problems as Saishy when upgraded to 4.x versions to 4.3.4
it starts with the "moving file failed"
I don't see a solution in this thread?

 

Just to weigh in here, I'm having the exact same problem. It's getting pretty annoying, even re-installing Unity completely is not helping

I can't yet verify if this is related but it seems that I started having this problem soon after installing a couple express versions of Visual Studio.

Edit: Also in my case it seems that breakpoints are only not working for certain files. In one script they don't work but in others they work fine. Of course I'm still having issues with the MonoDevelop Project getting out of sync.

 

I have the same problem.


This occurs 2 to 3 times a day because the file Library/ScriptAssemblies/Assembly-CSharp.dll.mdb is locked by MonoDevelop. When this happens, I simply close MonoDevelop, click Try Again then re-open MonoDevelop.

 

Ok well now I'm officially at my wit's end. I did a complete re-install of windows and right off the bat breakpoints still weren't working, and any error would cause Unity to totally crash. Then I got the Moving file failed error, closed Mono and now Mono won't open at all.

 

I'm facing the same problem while debugging on Android device: attaching to AndroidPlayer, breakpoints got desaturated and ignored. Even after deleting MonoDevelop-Unity-4.0 cache. The main development is under Visual Studio 2013 Express; MonoDevelop is used only for debugging.

Unity 4.3.2f1 Pro
Windows 8.1 Pro

 

Looks like running monodevelop as administrator fixes the problem. (and reimporting a script)

Its probably a OS blocking read/write files or something.

To repeat the bug

1) Attach monodevelop to Unity
2) Set a breakpoint
3) Execute
4) When the breakpoint is reached, click on play to continue (in monodevelop)
5) Modify the code and save
6) Get back to Unity

When triying to recompile, the Pop up shows up, crashing monodevelop and breaking the break points if you click on cancel.

 

I'm just getting started with Unity and Mono and I'm having these problems as well.

I consider myself still in the "pondering" stage of using Unity as I only have about 3 weeks invested into it. While Unity is one thing, the interfacing with Mono is, cough, makes me a bit ill.

The problem Mentioned above with the "Try again" to copy the executable code is caused by Mono having the code locked up, or in other words it is still attached to the code for debugging. Detach and then hit "Try again" and it works.

I have all of these problems and now the break points. This makes Unity worthless if one cannot debug it. I've had to uninstall Unity once already as it kept complaining about a library being within a library, or something silly like that. So when it started all it would do is put out a garbage message and shutdown. Since I'm new and didn't do much other than use it to simply add objects to the Hierarchy I was and still am surprised.

But back on topic, is there ANY relief to fixing breakpoints? I haven't found anything on the net but not being able to step into a method is not much of a debugger. And as I'm still evaluating this development platform I'm not willing to spend $100 to use Visual Studio to debug, and then find out that Unity is more hype and hacking then usable.

I'm using 4.3.4f1.

Question. I noticed that when I attach to Unity now that the textbox is empty. The one that says "Attach To". I don't know what was in it before as I ignored it and double clicked on Unity, but perhaps the tool is programmed in some strange fashion that some value has to be in the field to have it work correctly.

 

Thank God for backups. Restoring my project to yesterday's backup and Mono is working again. As only the project and files were restored (no Unity code) this points to project settings somehow messed it up. Comparing the SLN and other files don't show me anything that I recogninize as unusual, but I'm green at Mono and Unity.

 

Yes this occurs, when changing code of attached script in play mode. But what to do if click Cancel (to copy Assembly-CSharp.dll.mdb), then u can't get breakpoints work properly again?

 

Not hitting "Cancel", and going back to MonoDevelop, and hitting detach is good to know in the future. But if we had ALREADY hit cancel, and our breakpoints are now screwed, how do we unscrew them? Nothing I've found (in this thread, or others) has worked.

 

Well, I won't take this personally that God terrifies you. But as source control IS one of my two methods of backup, yes. But no hobby or professional development without another form of backup other than source control would be even more foolish. To rely on a single copy or single location for your 'backup' is asking for disaster.

 

If you have cancelled, delete Library/ScriptAssemblies. Then you should either right click on your Scripts folder and click re-import or restart Unity.

We have this problem here on every machine. The frequency of it happening is very variable but it's not anti-virus related, it happens with it disabled as well and the project folder is on the ignore list anyway.

It started happening with Unity 4.3/MonoDevelop, when recompiling while the debugger is attached. The odd thing is, recompiling doesn't always cause it, most of the time it works just fine, it's as if the debugger occasionally keeps the .mdb files locked.

 

The same thing happened to me. The failed to move error showed up and then break points can't be used afterwards.

 

I have the same problem!!!

 

Is this still a problem? I think I am debugging correctly for Unit 4.3.2f1, but I'm not hitting breakpoints and I'm brand new to unity. I followed the debugging steps earlier in the thread.... Any help?

 

Yes, it is a regression. We had never seen this problem before 4.3/MD4.0. It specifically became obvious because it manifested itself in a usage pattern we had been using for a year, keeping the debugger connected, stopping the game and recompiling.

 

I did not, because there were so many threads about it here and on Answers that I thought it'd be well reported already! If not, I can file one but it is tricky, as it is so intermittent that I cannot really submit a use case that consistently triggers it. I'll see if I can come up with an example project that does this frequently.

 

For me it worked by simply re-importing the scripts. Thanks.

 

A little bit old thread, but I might have found the solution. It appears that the files become locked because of adb.exe (it's the Android thingy). Simply kill adb.exe, delete your library files, open up your project, sync monodevelop project, put your breakpoints back, attach to process and press play, voila!

 

It worked for me. But the cache file always exist file, it means deleting the files before debugging each time...

Thanks anyway!!

 

I knew that it was something about the library folder but I couldn't be sure, so I just deleted the entire folder, which seemed to work. Anyway, the culprit is adb.exe which locks some files (probably "a" file) in ScriptAssemblies as you said. However, I am not sure why adb.exe is locking files, let alone running when you don't even select the publishing platform as Android.