Bug 11202 - Cannot delete watch without debugging unless you hack the userprefs file
Summary: Cannot delete watch without debugging unless you hack the userprefs file
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-03-16 14:12 UTC by Rhys
Modified: 2013-03-20 15:16 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Rhys 2013-03-16 14:12:04 UTC
If you by chance create a watch expression that will crash an iOS app in the Xamarin IDE, you will be unable to ever remove this watch, because the app will crash before you get a chance to. As soon as the app crashes, the watch entries are disabled, preventing you from removing them.

A workaround is to hack the userprefs file and manually remove the watch entries, but really this should be fixed up in the IDE. I don't see any logical reason behind disabling watch entries when the app is not running.
Comment 1 Jeffrey Stedfast 2013-03-20 15:09:31 UTC
The reason the debugger pads (locals, watches, ...)  get disabled when the debugger isn't running is because the code tries to evaluate stuff when you add/edit items.

Anyways, I agree that in the case of the Watch Window, this sucks.
Comment 2 Jeffrey Stedfast 2013-03-20 15:16:12 UTC
Implemented in git master