Bug 11067 - Xamarin Studio, cannot place breakpoints after adding a static class
Summary: Xamarin Studio, cannot place breakpoints after adding a static class
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-03-12 08:11 UTC by John Hair
Modified: 2013-08-05 12:55 UTC (History)
1 user (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 John Hair 2013-03-12 08:11:20 UTC
Whilst trying to replicate a different bug I created a new solution in XS (iOS, Phone, Single View Application).

After adding a simple static class with a static DoSomething() method that does nothing I could no longer put any breakpoints. Trying to compile resulted in a spinning beachball and I had to kill XS. Restarting XS and it behaves correctly.
Comment 1 Jeffrey Stedfast 2013-03-12 13:26:42 UTC
next time you get one of those spinning beachballs, could you open a terminal and use `ps ax | grep -i xamarin` to get the pid of Xamarin Studio and then run `kill -QUIT <pid>`?

This will force the Xamarin Studio to dump a stacktrace of each thread into ~/Library/Logs/XamarinStudio-4.0/Ide.log so we can see what is going on (probably a deadlock or a really slow section of code)

Thanks
Comment 2 Jeffrey Stedfast 2013-08-05 12:55:09 UTC
might have been related to a deadlock issue when adding breakpoints that I recently discovered/fixed