Hat es schon jemand geschafft ein Winforms C# App zum laufen zu bringen.   
Ein triviales HelloWorld mit Button und TextBox startet zwar, erscheint auf dem Screen crashed aber dann wie folgt :   
2015-05-05T22:35:58.643974+0200 
------------------------------------------------------------------------------- 
* Assertion at mini-codegen.c:807, condition `i == sel' not met   
Stacktrace:   
  at <unknown> <0xffffffff> 
  at System.Windows.Forms.TextBoxBase.Draw (System.Drawing.Graphics,System.Drawing.Rectangle) <0x000ab> 
  at System.Windows.Forms.TextBoxBase.OnPaintInternal (System.Windows.Forms.PaintEventArgs) <0x00063> 
  at System.Windows.Forms.Control.WmPaint (System.Windows.Forms.Message&) <0x0017f> 
  at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message&) <0x00217> 
  at System.Windows.Forms.TextBoxBase.WndProc (System.Windows.Forms.Message&) <0x00313> 
  at System.Windows.Forms.TextBox.WndProc (System.Windows.Forms.Message&) <0x001d3> 
  at System.Windows.Forms.Control/ControlWindowTarget.OnMessage (System.Windows.Forms.Message&) <0x0002b> 
  at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) <0x0003b> 
  at System.Windows.Forms.NativeWindow.WndProc (intptr,System.Windows.Forms.Msg,intptr,intptr) <0x0028b> 
  at System.Windows.Forms.XplatUIX11.DispatchMessage (System.Windows.Forms.MSG&) <0x00023> 
  at System.Windows.Forms.XplatUI.DispatchMessage (System.Windows.Forms.MSG&) <0x0002b> 
  at System.Windows.Forms.Application.RunLoop (bool,System.Windows.Forms.ApplicationContext) <0x00ac7> 
  at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext) <0x0005f> 
  at System.Windows.Forms.Application.Run (System.Windows.Forms.Form) <0x0002b> 
  at HelloWorld.Program.Main () <0x0003b> 
  at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>   
Native stacktrace:     
Debug info from gdb:   
[New LWP 17110] 
[Thread debugging using libthread_db enabled] 
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". 
0x76f01534 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0 
  Id   Target Id         Frame  
  2    Thread 0x75bf7430 (LWP 17110) "mono" 0x76f01534 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0 
* 1    Thread 0x76fee250 (LWP 17108) "mono" 0x76f01534 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0   
Thread 2 (Thread 0x75bf7430 (LWP 17110)): 
#0  0x76f01534 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0 
#1  0x76efe8c2 in do_futex_wait () from /lib/arm-linux-gnueabihf/libpthread.so.0 
#2  0x76efe92e in sem_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0 
#3  0x00187718 in mono_sem_wait () 
#4  0x00126222 in ?? () 
Backtrace stopped: previous frame identical to this frame (corrupt stack?)   
Thread 1 (Thread 0x76fee250 (LWP 17108)): 
#0  0x76f01534 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0 
#1  0x76f002f6 in waitpid () from /lib/arm-linux-gnueabihf/libpthread.so.0 
#2  0x000929e0 in ?? () 
Backtrace stopped: previous frame identical to this frame (corrupt stack?)   
================================================================= 
Got a SIGABRT while executing native code. This usually indicates 
a fatal error in the mono runtime or one of the native libraries  
used by your application. 
=================================================================