Bug 10584 - Debugger stops working
Summary: Debugger stops working
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-02-22 12:49 UTC by Alan McGovern
Modified: 2013-12-05 18:36 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 Alan McGovern 2013-02-22 12:49:20 UTC
I keep having to restart MD because the debugger thinks I'm in a paused session but i am actually not in any session. This means i can't start a debug session til I recycle MD. it's a recent issue, probably from the last few days.

It is very hard to get work done when you have to keep killing MD, restarting it, reloading the solution, recreating any required breakpoints and then praying you can get more than 1 debug session out of it before it gets confused.
Comment 1 Jeffrey Stedfast 2013-02-22 13:15:57 UTC
I don't seem to experience this and can't think of any recent changes that could have broken this.

do you have any more details?
Comment 2 PJ 2013-11-19 17:05:41 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:36:08 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.