1

Hey guys, I’m having a problem using the monodevelop debugger along with unity.
Every time I try to debug, the code will go to the break point and show the values on the Call Stack window, but not in the code window itself. So I can step through the code by calls but not by line.

It must be a problem in the Unity solution since I’ve tried reinstalling unity & monodevelop but continue to have this problem.

Here are my steps:

  • Unity->Sync with monodevelop
  • Monodevelop-> attach to process
  • Unity → Play
  • Monodevelop pauses at line but does not step through in code window

Any idea what could be causing this?

Thanks!!

2

Well Don’t I feel stupid :stuck_out_tongue:

I finally figured it out from the stack traces. I eventually noticed the code was calling the correct function but … in the wrong directories? Turns out after moving the unity file, unity decided to never re-import the files. So the code was being called correctly but the stack info being recived was wrong and monodevelop had no idea what to do with it.

So if you ever get this error… Just reimport all :slight_smile:

3

Addendum: If you happen to move your code, say from drive D to Drive E or to a different folder you have to import all again. Two of the symptoms you may notice are when trying to debug in Monodevelop are:

  1. When you hit a break point Monodevelop won’t show the current line of code. In the ‘call stack’ you’ll see the original source location if you happen to have this window open.

  2. In Unity, in the Process tab you won’t see any compilation warnings or errors, similar as to when Monodevelop has the wrong project open.