Bug 3688 - Compiler crash on MonoTouch 5.2.5
Summary: Compiler crash on MonoTouch 5.2.5
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2012-02-29 14:33 UTC by Miguel de Icaza [MSFT]
Modified: 2012-03-01 03:28 UTC (History)
1 user (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 Miguel de Icaza [MSFT] 2012-02-29 14:33:47 UTC
using System.Threading.Tasks;
using System;

class X {
static void Main () {}

public static Task<T> NetworkBackground<T>(Func<T> func)
var task = new Task<T>(func);


task.ContinueWith((finishedTask) => delegate {
if (finishedTask.IsFaulted)

return task;
Comment 2 Marek Safar 2012-02-29 14:46:52 UTC
Already fixed in master.

This code is actually invalid, the user is confusing anonymous methods and lambda expressions.

The code should probably be written as

task.ContinueWith((finishedTask) => {
Comment 3 Miguel de Icaza [MSFT] 2012-02-29 15:18:57 UTC
Any chance we can get this backported?
Comment 4 Marek Safar 2012-03-01 03:28:01 UTC
Not without trying to fix it again in 2.10, the mcs is quite different to (reflection based gmcs)