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
GitHub or Developer Community 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.
Repeatability: Intermittent but often
When choosing to step in to code, the debugger often does not step in and ends up breaking at some other location.
Example: see '1.' and '2' for the order of what happens
for(int i = 0; i < Nodes.Count; i++) --- 2. 'Step Into' actually steps over and this is now the 'current' line
Nodes[i].RenderToContext(context, m_screenBufferContext, MapView.Bounds); --- 1. attempt to 'Step Into' here
Try turning off the 'Automatically step over properties and operators' option in preferences/debugger.
This did enable me to debug properly. I am almost positive this problem has occurred when this option was turned off. I will re-open this bug if I see that again. Thanks.