Bug 1322 - MonoDevelop 2.8 Crashes on Debug Build
Summary: MonoDevelop 2.8 Crashes on Debug Build
Status: RESOLVED DUPLICATE of bug 1213
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-06 17:00 UTC by Ian
Modified: 2011-10-08 20:51 UTC (History)
5 users (show)

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

Symbolic info (81.91 KB, text/rtf)
2011-10-06 17:00 UTC, Ian

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 Ian 2011-10-06 17:00:34 UTC
Created attachment 631 [details]
Symbolic info

No idea why or how. Here's the dump:
Comment 1 Rolf Bjarne Kvinge [MSFT] 2011-10-06 17:09:33 UTC
The first impression I get is that the size of the stack trace indicates that it might be a stack overflow (and the GC related parts at the top are quite normal) - otoh the stack isn't that big either.

However I understand it does not happen with release builds? What about on device? Does it happen every time and/or in a specific place in your code, or is it random?
Comment 2 Ian 2011-10-06 17:16:03 UTC
Turns out it happens all the time. When I right click the main project and choose BUild.

I have 4 projects based on MonoDialog in this solution. Only the main project does it.

I converted the project to VS 2010 format using the MonoDevelop tool that asked if I wanted to.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2011-10-06 17:23:59 UTC
Oh, sorry about that I thought it was a MonoTouch application that was crashing, not MonoDevelop.

In any case quickest way to fix it would be if we got access to the project it's happening with so that we can reproduce it ourselves (if that's not possible I explain how to get more information, but it will all take a bit longer).
Comment 4 Glenn Stephens 2011-10-07 00:07:39 UTC
I too am getting the same issue. 

I have a project with six libraries that I have included with the project as well as the main application. Debugging on the simulator and the device is not possible at all. 

The error message on the final project when compiling is "Build failed. Object reference not set to an instance of an object" on the file project (executable) build.
Comment 5 Ian 2011-10-07 01:05:08 UTC
I removed the project file, made a new one and re- included all the files. Now MonoDevelop does not crash.

The project was converted by MonoDevelop to the new format, perhaps the issue was there.
Comment 6 Rolf Bjarne Kvinge [MSFT] 2011-10-07 03:08:13 UTC
Glenn: you're issue is different, can you add to mtouch's additional arguments (right-click the project -> Options -> iPhone Build -> Additional mtouch arguments) "-v -v -v -v" (without the quotes, rebuild again and attach the build log to a new bug report?

Ian: you wouldn't happen to have the old project so that we can figure out what happened?
Comment 7 Sebastien Pouliot 2011-10-07 09:43:22 UTC
Ian, that looks like a duplicate of bug #1213 and (for me) only happens in some situation where the code should not compile
Comment 8 Ian 2011-10-07 11:38:06 UTC

No, sorry, I got rid of it.

Comment 9 Rolf Bjarne Kvinge [MSFT] 2011-10-07 17:48:53 UTC
Ok, I'm closing this bug report then.
Comment 10 Sebastien Pouliot 2011-10-07 18:33:50 UTC
I prefer dupe to invalid ;-) not sure it's the same cause but it looks like the same crash

*** This bug has been marked as a duplicate of bug 1213 ***
Comment 11 Glenn Stephens 2011-10-08 20:51:29 UTC
Rolf, it turns out it is something else. See bug 1370