Bug 299 - Monodevelop crashed when using runtime debug logging
Summary: Monodevelop crashed when using runtime debug logging
Status: RESOLVED DUPLICATE of bug 165
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.6 Beta 3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-08-15 17:15 UTC by Ian
Modified: 2011-08-23 10:02 UTC (History)
3 users (show)

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


Attachments
Debug log (107.82 KB, application/octet-stream)
2011-08-15 17:15 UTC, Ian
Details
crash (59.90 KB, image/jpeg)
2011-08-15 18:02 UTC, Ian
Details


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 DUPLICATE of bug 165

Description Ian 2011-08-15 17:15:27 UTC
Created attachment 130 [details]
Debug log

When I run these commands in Terminal then try to open a project I get the attached crash debug log.

export MONO_OPTIONS=--trace=E:all
export MONO_LOG_MASK=asm
export MONO_LOG_LEVEL=debug

open /Applications/MonoDevelop.app

I am attempting to load a project from a shared drive.

In non-debug mode it works fine.
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-15 17:52:39 UTC
What's the Mono version? Do you have an actual crash trace from the apple crash reporter dialog?
Comment 2 Ian 2011-08-15 18:02:33 UTC
Created attachment 133 [details]
crash
Comment 3 Ian 2011-08-15 18:08:17 UTC
The Mono version is 2.10.4. I attached the crash image
Comment 4 Mikayla Hutchinson [MSFT] 2011-08-15 18:41:03 UTC
If the app hard crashed the Apple crash reporter dialog should have come up. Please copy the detail text from it.
Comment 5 Ian 2011-08-15 18:43:37 UTC
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.
Comment 6 Mikayla Hutchinson [MSFT] 2011-08-15 18:46:56 UTC
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.
Comment 7 Ian 2011-08-15 18:49:30 UTC
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
Comment 8 Ian 2011-08-15 18:55:20 UTC
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
Comment 9 Mikayla Hutchinson [MSFT] 2011-08-15 18:57:31 UTC
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?
Comment 10 Ian 2011-08-15 19:01:24 UTC
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.
Comment 11 Miguel de Icaza [MSFT] 2011-08-23 10:02:31 UTC

*** This bug has been marked as a duplicate of bug 165 ***