Bug 284 - Error in the Select device dialog
Summary: Error in the Select device dialog
Alias: None
Product: Runtime
Classification: Mono
Component: io-layer ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-08-12 12:30 UTC by Rodrigo Kumpera
Modified: 2011-11-23 10:33 UTC (History)
3 users (show)

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 GitHub or Developer Community 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 Rodrigo Kumpera 2011-08-12 12:30:59 UTC
I'm Lion / mono 2.10.4 / md 2.6b3.

Steps to reproduce:

-Create a new Android app project and compile it;
-Make sure you have no android device connected;
-Click run, you should end in the "Select Device" modal dialog;
-Click the "Refresh Devices" button as fast as you can.

MD will eventually pop up an exception dialog and die once closed. It has the following exception: 

System.NullReferenceException: Object reference not set to an instance of an object
  at MonoDevelop.MonoDroid.AdbStartServerProcess.CaptureOutput () [0x00000] in <filename unknown>:0 
  at System.Threading.Thread.StartUnsafe () [0x00016] in /private/tmp/monobuild/build/BUILD/mono-2.10.4/mcs/class/corlib/System.Threading/Thread.cs:680
Comment 1 Alan McGovern 2011-11-14 16:56:28 UTC
This looks like a runtime bug:

* Assertion at mini-darwin.c:151, condition `result == MACH_MSG_SUCCESS' not met

Native stacktrace:

	0   mono                                0x000b90c6 mono_handle_native_sigsegv + 422
	1   libsystem_c.dylib                   0x9407159b _sigtramp + 43
	2   ???                                 0xffffffff 0x0 + 4294967295
	3   libsystem_c.dylib                   0x9400cbdd abort + 167
	4   mono                                0x0025186d monoeg_g_logv + 197
	5   mono                                0x002518e3 monoeg_assertion_message + 46
	6   mono                                0x0010a446 mach_exception_thread + 230
	7   mono                                0x0026a481 GC_start_routine + 107
	8   libsystem_c.dylib                   0x94019ed9 _pthread_start + 335
	9   libsystem_c.dylib                   0x9401d6de thread_start + 34
Comment 2 Rodrigo Kumpera 2011-11-23 10:33:28 UTC
I can't repro it anymore :(