Bug 4018 - Debugger says "could not resolve breakpoint" when it really did
Summary: Debugger says "could not resolve breakpoint" when it really did
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-03-21 16:09 UTC by Jeffrey Stedfast
Modified: 2012-03-21 16:15 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 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 Jeffrey Stedfast 2012-03-21 16:09:25 UTC
As seen in this video cast (with a sharp eye!), you can see in the Application Output window that MonoDevelop claims to have failed to resolve the breakpoint in the body of the delegate on line 30. BUT the very next line, it prints a message saying it resolved it.


The truth is that we ARE resolving it, it's just that the error is printed because we failed to resolve it in Activity1.OnCreate(), because it's *actually* in a compiler-generated class.
Comment 1 Jeffrey Stedfast 2012-03-21 16:15:52 UTC
Fixed in git master & 2.8.8-series