Bug 514 - Exception when removing break point
Summary: Exception when removing break point
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.6 RC 1
Hardware: PC Windows
: High major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-08-29 04:55 UTC by Ox2CEF
Modified: 2011-12-29 02:56 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 Ox2CEF 2011-08-29 04:55:43 UTC
When add break point in some delegate it is not active. When remove Exception trows:

System.NullReferenceException: Object reference not set to an instance of an object.

   at MonoDevelop.Debugger.Win32.CorDebuggerSession.OnRemoveBreakEvent(BreakEventInfo bi)

   at Mono.Debugging.Client.DebuggerSession.RemoveBreakEvent(BreakEvent be)
Comment 1 Jeffrey Stedfast 2011-11-29 11:18:48 UTC
Adding a breakpoint inside a delegate works fine in master (and it is active).

Removing said breakpoint also works without throwing any exceptions.
Comment 2 Saurabh 2011-12-29 02:56:16 UTC
We have verified this issue with MonoDevelop 2.8.5 and MonoTouch 5.0.4,it is no longer exist.

Kindly close this issue.