Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Often, while debugging when im stepping through code, or jumping from one breakpoint to another, the currently executed line becomes un-highlighted, but the code never moves to the next line. No line is highlighted as the current line.
THe app on the device itself is frozen (as it usually is while debugging). The step into, step over and run buttons/commands are disabled. I have no choice but to stop debugging and try again.
It happens randomly, I could run the exact same build 5 times, and it could happen randomly on a different line of code each time.
Dermot: when MonoDevelop 2.8.5 and MonoTouch 5.0.4 are released in the next few days, could you test those out and see if you can still reproduce this?
There's been a number of fixes to the debugger code.
I recognize that it's a "doesn't always happen" bug, so it'll likely take a few days of testing before you can feel sure that it's no longer an issue (assuming you don't reproduce it!), so no rush.
I'm going to mark as NEEDINFO for now since I've not seen this.
This seems to be narrowed down to when an exception occurs in a thread (such as a threadpool thread). There is no feedback that there was an error, the debugger just doesn't move to the next line
Ok, I've narrowed this down further. It seems to be occurrig the first time a method is called from a referenced dll.
Its pretty common. For every 10 times I start a debug, it might happen maybe 6 times. It really slows down development.
This is FAR far better than it used to be. It does still happen, but is much rarer.
Mono 2.10.9 (tarball)
Package version: 210090011
Apple Developer Tools:
Xcode 4.4.1 (1488)
Mono for Android: Not Installed
Thanks for keeping us updated.
I might need to get the runtime guys involved in this one.
Zoltan: any ideas?
Setting the env variable MONO_SDB_ENV_OPTIONS to 'loglevel=10' produces lots of debugging output on stdout, that might help in diagnosing the problem.
Has this been fixed, by any chance?
I've started to experience this lately myself...
just as a reminder to myself: this doesn't seem to be iPhone related because I've been getting this behavior while debugging Xamarin Studio inside Xamarin Studio.
haven't seen this in ages