Bug 5066 - Breakpoints not hit when using anonymous code
Summary: Breakpoints not hit when using anonymous code
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.1.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-14 13:37 UTC by Goncalo Oliveira
Modified: 2013-10-23 13:58 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 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:

Description Goncalo Oliveira 2012-05-14 13:37:53 UTC
Breakpoints set in anonymous code aren't hit.

Consider the following method as an example

Something.ExecuteAsync( Action<T> response );

and the code...

Something.ExecuteAsync( ( response ) =>
   ... breakpoint here is not hit
} );

This did not happen in the previous stable release.
Comment 1 Jonathan Pobst 2012-05-14 14:31:58 UTC
Are you using Visual Studio or MonoDevelop?
Comment 2 Jonathan Pobst 2012-05-14 17:25:18 UTC
Fixed in 322fe1db63120f4117d8baa454171e0ff3858f83.
Comment 3 Diego F 2013-10-23 13:58:57 UTC
It is still happening using Visual Studio, Xamarin.iOS, Xcode 5.0, Xamarin Studio 4.0.13(build 38).