- Home /
Monodevelop debugging
Just started to utilize debugging through monodev in Unity and I'm having some strange problems that I want to make sure aren't standard behavior.
The first issue is that when I set a breakpoint in my code to fall on a function declaration, the debugger totally ignores it. I can have a function like this:
public void DoStuff()
{
// Do something
}
If I were to place the breakpoint on the line with the function name, the debugger acts as if the function isn't there, even though everything works fine when playtesting within the editor. If I were to put the breakpoint anywhere else, the debugger will stop on that line like it's supposed to. Why is this? Are you just not supposed to place breakpoints on the first line of a function?
The second (and more serious) issue is that when stepping through lines of code, if I were to completely step through a function and then keep stepping through the script so that it exits the last set of curly braces in the script, upon returning to the unity editor everything will slow to a crawl. I'm talking one frame every 3-4 seconds. If I were to hit F5 in monodev to continue BEFORE I reach the bottom of the script, it will return to unity just fine and everything will still behave at the appropriate speed. Am I always supposed to hit continue before the debugger reaches the bottom of a script? This seems very awkward if so, or maybe I'm just used to how nice debugging in Visual Studio is.
Your answer
Follow this Question
Related Questions
Breakpoints stopped triggering in MonoDevelop 4.0.1 4 Answers
How to access static members in the watch/immediate window when debugging with MonoDevelop 0 Answers
Is it possible to debug Unity games using Monodevelop 3? 2 Answers
MonoDevelop not recognizing commands or errors on new scripts 0 Answers
Why does monodevelop sets "pink", nonfunctioning breakpoints ? 1 Answer