Bug 3041 - MonoDevelop crash when stopping the debugger
Summary: MonoDevelop crash when stopping the debugger
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2012-01-24 13:56 UTC by Jackson Harper
Modified: 2013-04-02 15:40 UTC (History)
2 users (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 Jackson Harper 2012-01-24 13:56:10 UTC
The debugger had never even attached (see bug #3040)

Crash log:

Starting MonoDevelop
   Loading Workbench
      Initializing Main Window
MacDir exists
Basedir=/Library/Frameworks/Mono.framework/Versions/2.10.8.1/lib/monodoc
MacDir exists
Basedir=/Library/Frameworks/Mono.framework/Versions/2.10.8.1/lib/monodoc
ERROR [2012-01-24 13:25:25Z]: Error in debugger
Mono.Debugging.Soft.DisconnectedException: The connection with the debugger has been lost. The target application may have exited.
ERROR [2012-01-24 13:27:53Z]: Error in debugger
Mono.Debugging.Soft.DisconnectedException: The connection with the debugger has been lost. The target application may have exited.
ERROR [2012-01-24 13:28:08Z]: Error in debugger
Mono.Debugging.Soft.DisconnectedException: The connection with the debugger has been lost. The target application may have exited.
Stacktrace:

  at (wrapper managed-to-native) Gtk.Application.gtk_main () <IL 0x00022, 0xffffffff>
  at Gtk.Application.Run () <IL 0x00000, 0x0000b>
  at MonoDevelop.Ide.IdeApp.Run () [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.3/f4289daf/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/Ide.cs:384
  at MonoDevelop.Ide.IdeStartup.Run (MonoDevelop.Ide.MonoDevelopOptions) [0x00688] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.3/f4289daf/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:272
  at MonoDevelop.Ide.IdeStartup.Main (string[]) [0x0004f] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.3/f4289daf/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:503
  at MonoDevelop.Startup.MonoDevelopMain.Main (string[]) [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.3/f4289daf/source/monodevelop/main/src/core/MonoDevelop.Startup/MonoDevelop.Startup/MonoDevelopMain.cs:16
  at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <IL 0x0005c, 0xffffffff>

Native stacktrace:

	0   monodevelop                         0x00094eec mono_handle_native_sigsegv + 284
	1   monodevelop                         0x00004fd8 mono_sigsegv_signal_handler + 248
	2   libsystem_c.dylib                   0x976f959b _sigtramp + 43
	3   ???                                 0xffffffff 0x0 + 4294967295
	4   AppKit                              0x93e528ab -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
	5   libgdk-quartz-2.0.0.dylib           0x04495b6d poll_func + 317
	6   libglib-2.0.0.dylib                 0x03da5dfc g_main_context_poll + 280
	7   libglib-2.0.0.dylib                 0x03da5107 g_main_context_iterate + 1183
	8   libglib-2.0.0.dylib                 0x03da5987 g_main_loop_run + 992
	9   libgtk-quartz-2.0.0.dylib           0x04045540 gtk_main + 240
	10  ???                                 0x10454f2c 0x0 + 272977708
	11  ???                                 0x10454ef4 0x0 + 272977652
	12  ???                                 0x10454ed4 0x0 + 272977620
	13  ???                                 0x02cf009c 0x0 + 47120540
	14  ???                                 0x004a5f90 0x0 + 4874128
	15  ???                                 0x004a5d9c 0x0 + 4873628
	16  ???                                 0x004a5e56 0x0 + 4873814
	17  monodevelop                         0x0000d272 mono_jit_runtime_invoke + 722
	18  monodevelop                         0x001a435a mono_runtime_invoke + 170
	19  monodevelop                         0x001a6e9c mono_runtime_exec_main + 620
	20  monodevelop                         0x001a6101 mono_runtime_run_main + 929
	21  monodevelop                         0x00069985 mono_jit_exec + 149
	22  monodevelop                         0x0006bf03 mono_main + 9587
	23  monodevelop                         0x00002289 main + 441
	24  monodevelop                         0x00002096 start + 54
	25  ???                                 0x00000005 0x0 + 5

Debug info from gdb:


=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================
Comment 1 Jeffrey Stedfast 2013-04-02 15:40:13 UTC
not sure we can get anything useful out of this crash/backtrace

possibly one of the multithreading issues I fixed in the debugger (i.e. threads calling into gtk)