Bug 5701 - Step into method not working well with Step Over Properties option
Summary: Step into method not working well with Step Over Properties option
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger ()
Version: 2.10.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2012-06-18 06:58 UTC by Lluis Sanchez
Modified: 2015-02-20 12:12 UTC (History)
2 users (show)

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


Attachments
Test case (50.92 KB, image/png)
2012-06-18 06:58 UTC, Lluis Sanchez
Details


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:
Status:
RESOLVED FIXED

Description Lluis Sanchez 2012-06-18 06:58:37 UTC
Created attachment 2075 [details]
Test case

Consider the test case shown in the attached screenshot. When the debugger stops in the breakpoint I click on Step Into. I have the "Step Over properties" option set, so the expected behavior is for the debugger to skip the property and stop in the Write method. Instead, the debugger does what the screenshot shows: it skips the Write method entirely, and steps into the next method call.
Comment 1 Zoltan Varga 2012-06-18 07:06:08 UTC
What mono version is this ? This should be fixed in master.
Comment 2 Lluis Sanchez 2012-06-18 07:21:01 UTC
Mono 2.10.9
Comment 3 Jeffrey Stedfast 2015-02-20 12:12:36 UTC
fixed