Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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 220.127.116.11 as I never seen this before this morning.
crash in what? MonoDevelop? or an app you were debugging?
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)
this seems to suggest that DebuggerSession's slock is being held.
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.