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.
Created attachment 2861 [details]
Screenshot of the error
Win7, Monodevelop 3.0.5
If you move mouse over the class name (in new statement), it evaluates Cairo.Color value several seconds. Then '+' icon appears. If I click the icon, it disappers :-)
If I compare Monodevelop debugging with VisualStudio debugging I can say that:
1. MonoDevelop debugging is very slow in evaluting values.
2. MonoDevelop debugging is very buggy: empty content of evaluation window, object is in a zombie state, null exceptions, etc.
3. MonoDevelop debugging is practically not possible.
Please, I somebody can, do it something with it...
You need to use the Mono SoftDebugger and not the Windows CorDebugger, but in order to do so, you'll need to install Mono and debug your app under Mono and not .NET
How I can do that? If I switch in Monodevelop from 'Default Runtime' to 'Mono 2.10.8' or 'Mono 2.11.3', debugging doesn't work at all. I set breakpoint and run app (F5), but the app is not stopped by the debugger.
Make sure you completely rebuild your app, since the Mono debugger uses a different debug info file format.
Oh, It didn't come to my mind. So, I've rebuilt it and the debugger stopped the app. That is fine. But if I move mouse over the 'c' variable, which is of Cairo.Context type, mono.exe stops working. I tried that more than once and in the several cases the whole MonoDevelop got stuck. I had to kill MonoDevelop process.
Perhaps some problem with evaluating Cairo.Context ?
You can see that in the attachment.
Created attachment 2863 [details]
MonoDevelop debugging error
Created attachment 2864 [details]
MonoDevelop debugging jam
Everything with the CorDebugger except the evaluation tooltip not being updated unless hovering back is fixed. :D
All these CorDebugger issues have been fixed.