Bug 2008 - Debugger crash iOS
Summary: Debugger crash iOS
Status: RESOLVED DUPLICATE of bug 1214
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-11-11 09:14 UTC by kenny goers
Modified: 2011-12-29 06:47 UTC (History)
3 users (show)

Tags: gtk
Is this bug a regression?: ---
Last known good build:

Debugger Crash Log TEXT (84.96 KB, text/plain)
2011-11-11 09:14 UTC, kenny goers

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 kenny goers 2011-11-11 09:14:15 UTC
Debugger/MonoDevleop crash while attempting to debug iOS Simulator, crash log attached.
Comment 1 kenny goers 2011-11-11 09:14:46 UTC
Created attachment 875 [details]
Debugger Crash Log TEXT
Comment 2 Alan McGovern 2011-11-23 14:04:43 UTC
Can you reproduce this issue frequently or was this a one-time issue?  If it's possible to reproduce it frequently, would you be able to supply a list of steps which we can follow to cause the crash? Alternatively could you create a screencast? There are some known issues which have been resolved internally but I'm unsure whether or not they fix this particular issue as the stacktrace is slightly different.
Comment 3 Alan McGovern 2011-11-28 05:37:53 UTC
Bug 1214 has a log with the same stacktrace, so likely the same issue.

*** This bug has been marked as a duplicate of bug 1214 ***
Comment 4 Saurabh 2011-12-29 06:47:53 UTC
Unable to verify this issue because bug 1214 is in progress.