Bug 6698 - Add or remove a breakpoint fails when app is suspended on iOS device
Summary: Add or remove a breakpoint fails when app is suspended on iOS device
Status: RESOLVED DUPLICATE of bug 12673
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-08-27 05:08 UTC by Matthijs Koopman
Modified: 2013-06-14 13:08 UTC (History)
1 user (show)

Tags: debugger, crash
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 Matthijs Koopman 2012-08-27 05:08:37 UTC
The case as described below will cause MonoDevelop to hang and eventually crash:

1: start debugging an iPhone / MonoTouch application (on simulator, didn't test on device)
2: place the iPhone app (in simulator) into the background (press the home button on the simulator)
3: try to add or remove a breakpoint

This will cause mono develop to freeze and eventually crash
Comment 1 Jeffrey Stedfast 2012-08-27 12:41:22 UTC
Hmm, probably because the app is suspended on the device and isn't replying to our requests.

We probably need to find a more fault-tolerant way of handling this.
Comment 2 Jeffrey Stedfast 2013-06-14 13:08:40 UTC
Happened to get a stack trace of this happening and was able to find a way to fix it

*** This bug has been marked as a duplicate of bug 12673 ***