Bug 3416 - Better stack trace for iterators
Summary: Better stack trace for iterators
Status: RESOLVED DUPLICATE of bug 2671
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-02-13 07:59 UTC by Marek Safar
Modified: 2012-02-13 11:38 UTC (History)
1 user (show)

Tags:
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 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 DUPLICATE of bug 2671

Description Marek Safar 2012-02-13 07:59:47 UTC
using System;
using System.Collections.Generic;

class C
{
	public static void Main ()
	{
		var c = new C ();
		foreach (var a in c.Iter_1 ())
		{
		}
	}
	
	IEnumerable<int> Iter_1 ()
	{
		yield return 1;	// Set a breakpoint here
	}
}

Stacktrace window

MD

C+<Iter_1>c__Iterator0.MoveNext ()
C.Main ()

VS

C.Iter_1.MoveNext()
C.Main()
Comment 1 Mikayla Hutchinson [MSFT] 2012-02-13 11:38:29 UTC

*** This bug has been marked as a duplicate of bug 2671 ***