Bug 10590 - Stepping into a foreach over a yielded method call takes many steps
Summary: Stepping into a foreach over a yielded method call takes many steps
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-02-22 14:44 UTC by Eric Maupin
Modified: 2013-03-27 19:48 UTC (History)
2 users (show)

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


Attachments
Repro project (13.98 KB, application/octet-stream)
2013-02-22 14:44 UTC, Eric Maupin
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 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.

Related Links:
Status:
RESOLVED FIXED

Description Eric Maupin 2013-02-22 14:44:39 UTC
Created attachment 3458 [details]
Repro project

Stepping into a foreach over a method that utilizes "yield" results in numerous step-intos with [External code] at the top of the call stack before it will actually enter the method.

In the attached project, place a breakpoint on the foreach keyword line. When debugging breaks on this line, attempt to "step in".
Comment 1 Eric Maupin 2013-02-22 16:45:52 UTC
Tested with VS2012
Comment 2 Jeffrey Stedfast 2013-03-27 19:48:50 UTC
fixed in git master (VS will need to pull the fix over)