Bug 11804 - Xamarin Studio crashes in GC code when launching debug (simulator and device)
Summary: Xamarin Studio crashes in GC code when launching debug (simulator and device)
Status: RESOLVED NORESPONSE
Alias: None
Product: Runtime
Classification: Mono
Component: GC ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-04-16 09:20 UTC by Marc-Alex. Berube
Modified: 2017-07-07 20:58 UTC (History)
7 users (show)

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


Attachments
Crash log (81.99 KB, application/octet-stream)
2013-04-16 09:20 UTC, Marc-Alex. Berube
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 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:
Status:
RESOLVED NORESPONSE

Description Marc-Alex. Berube 2013-04-16 09:20:17 UTC
Created attachment 3816 [details]
Crash log

I have installed Xamarin Studio on another computer this morning. I have fetched my application from a git repository and tried to debug it. 

While it used to work fine on my iMAC (2007), now it crashed few minutes after launch on simulator (or device) in debug mode. Attachment is my crash log.

The app first crash on the simulator then Xamarin Studio crash right after.


My iMac is currently running OSX Lion while the Macbook Pro is running Mountain Lion. But my colleague is running mountain lion and have no problem running it
Comment 1 Mikayla Hutchinson [MSFT] 2013-04-20 00:17:15 UTC
From the log, this appears to be a SIGILL in the GC:

0   libsystem_kernel.dylib        	0x94a37a6a __pthread_kill + 10
1   libsystem_c.dylib             	0x93b8eb2f pthread_kill + 101
2   libsystem_c.dylib             	0x93bc54ec abort + 168
3   libmonosgen-2.0.dylib         	0x01093900 mono_handle_native_sigsegv + 624
4   libmonosgen-2.0.dylib         	0x01003f48 mono_sigsegv_signal_handler + 248
5   libsystem_c.dylib             	0x93b798cb _sigtramp + 43
6   ???                           	0xffffffff 0 + 4294967295
7   libmonosgen-2.0.dylib         	0x01003e50 mono_sigill_signal_handler + 64
8   libmonosgen-2.0.dylib         	0x011f34ba mono_gc_alloc_obj_nolock + 458
9   libmonosgen-2.0.dylib         	0x011f3eba mono_gc_alloc_string + 170
10  libmonosgen-2.0.dylib         	0x011ae48a mono_string_new_size + 170
11  libmonosgen-2.0.dylib         	0x012222b0 ves_icall_System_String_InternalAllocateStr + 32
Comment 2 Mikayla Hutchinson [MSFT] 2013-04-22 14:10:24 UTC
This has been reported as working with Mono 3.0.10, so we can close it when 3.x is released to stable, if it's not fixed in 2.10.x.
Comment 3 Mikayla Hutchinson [MSFT] 2013-04-22 18:02:45 UTC
The reporter mentioned via email that this happens with Mono 2.10.12 but not Mono 2.10.11, so it may be a regression introduced in Mono 2.10.12.
Comment 4 Rodrigo Kumpera 2013-04-23 14:18:36 UTC
There are no commits between 2.10.11 and 2.10.12 that could trigger such crash.

How do could I repro this crash?
Comment 5 Mikayla Hutchinson [MSFT] 2013-04-30 17:50:16 UTC
*** Bug 12044 has been marked as a duplicate of this bug. ***
Comment 6 Mikayla Hutchinson [MSFT] 2013-04-30 19:05:53 UTC
*** Bug 12044 has been marked as a duplicate of this bug. ***
Comment 7 Ludovic Henry 2017-07-07 20:58:22 UTC
Can you still reproduce this bug? Please feel free to reopen if that still the case. Thank you.