Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 130 [details]
When I run these commands in Terminal then try to open a project I get the attached crash debug log.
I am attempting to load a project from a shared drive.
In non-debug mode it works fine.
What's the Mono version? Do you have an actual crash trace from the apple crash reporter dialog?
Created attachment 133 [details]
The Mono version is 2.10.4. I attached the crash image
If the app hard crashed the Apple crash reporter dialog should have come up. Please copy the detail text from it.
The app doesn't crash, it's the debugger. Have a look at the screen shot I included. It's just a .NET standard Exception screen the MonoDevelop puts up for Unhandled Exceptions.
I did look at the screenshot. It's not a crash, and it's not clear to me whether you're reporting a crash or the unhandled exception.
Yes,in that context I am reporting:
An UnHandled Exception thrown by MonoDevelop when a MonoTouch application(any) is run in debug mode.
I use Mono 2.10.4 and MonoDevelop 2.6b3
Reverting to MonoDevelop 2.4 solves the issue, but I'd rather use 2.6
Here's the UnHandled Exception Stack that pops up.:
System.TypeLoadException: A type load exception has occurred.
at MonoDevelop.Debugger.DebuggerEngine.CreateDebuggerStartInfo (MonoDevelop.Core.Execution.ExecutionCommand cmd) [0x00006] in /Users/michael/Mono/md-2-6/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebuggerEngine.cs:82
at MonoDevelop.Debugger.DebuggingService.InternalRun (MonoDevelop.Core.Execution.ExecutionCommand cmd, MonoDevelop.Debugger.DebuggerEngine factory, IConsole c) [0x0003a] in /Users/michael/Mono/md-2-6/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebuggingService.cs:483
at MonoDevelop.Debugger.DebugExecutionHandler.Execute (MonoDevelop.Core.Execution.ExecutionCommand command, IConsole console) [0x00000] in /Users/michael/Mono/md-2-6/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebugExecutionHandlerFactory.cs:70
at MonoDevelop.Debugger.DebugExecutionHandlerFactory.Execute (MonoDevelop.Core.Execution.ExecutionCommand command, IConsole console) [0x00015] in /Users/michael/Mono/md-2-6/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebugExecutionHandlerFactory.cs:52
at MonoDevelop.Projects.DotNetProject.DoExecute (IProgressMonitor monitor, MonoDevelop.Projects.ExecutionContext context, MonoDevelop.Projects.ConfigurationSelector configuration) [0x000b2] in /Users/michael/Mono/md-2-6/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/DotNetProject.cs:1141
That exception is bug 165, should I mark this as a duplicate or is there another issue here? The original post seemed to imply that enabling runtime tracing was causing a crash.
What's the reason you're running with runtime tracing?
IN a previous bug I was asked by Rolf to turn on debug tracing, I thought it was needed to provide information to this bug. I have disabled tracing.
*** This bug has been marked as a duplicate of bug 165 ***