Bug 3702 - Breakpoint pad disabled (after crash)
Summary: Breakpoint pad disabled (after crash)
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8.6
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-03-01 09:30 UTC by Sebastien Pouliot
Modified: 2012-04-12 17:37 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

screenshot (421.33 KB, image/png)
2012-03-01 09:30 UTC, Sebastien Pouliot

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 Sebastien Pouliot 2012-03-01 09:30:47 UTC
Created attachment 1445 [details]

After a crash (could be unrelated) the Breakpoint pad is disabled. I also cannot remove existing (or add new) breakpoints. 

However re-starting the application will break on the existing (readonly) breakpoints.

Might be new in MD as I never seen this before this morning.
Comment 1 Jeffrey Stedfast 2012-03-01 13:00:07 UTC
crash in what? MonoDevelop? or an app you were debugging?
Comment 2 Sebastien Pouliot 2012-03-01 13:07:03 UTC
The application I was debugging. 

Restarting MD "fixed" it - but it looks like there's a condition where the pad does not get re-enabled once the application dies (and is restarted under the debugger)
Comment 3 Jeffrey Stedfast 2012-03-05 10:01:11 UTC
this seems to suggest that DebuggerSession's slock is being held.
Comment 4 Jeffrey Stedfast 2012-04-12 17:37:02 UTC
I fixed some multithreaded debugger issues a while back so closing with the hope that this is now "FIXED"

if you get this again in >= 2.9.4, let me know.