Bug 12696 - Step Into results in odd behavior
Summary: Step Into results in odd behavior
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
Depends on:
Reported: 2013-06-14 13:29 UTC by brandon
Modified: 2013-06-17 13:05 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description brandon 2013-06-14 13:29:46 UTC
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
Comment 1 Zoltan Varga 2013-06-15 19:28:19 UTC
Try turning off the 'Automatically step over properties and operators'  option in preferences/debugger.
Comment 2 brandon 2013-06-17 13:05:54 UTC
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.