Comment 1 for bug 237724

Linux srv1 2.6.24-19-xen #1 SMP Wed Jun 4 17:03:44 UTC 2008 x86_64 GNU/Linux

Same deal here with 2.6.24-19-xen on AMD64 - No mono applications work, f-spot example below.

# f-spot
TYPE: 1
**
** ERROR:(mini-amd64.c:192):amd64_patch: assertion failed: (amd64_is_imm32 (disp))
Stacktrace:

Native stacktrace:

        f-spot [0x51bb67]
        /lib/libpthread.so.0 [0x7f39dde0e7d0]
        /lib/libc.so.6(gsignal+0x35) [0x7f39dd84f095]
        /lib/libc.so.6(abort+0x110) [0x7f39dd850af0]
        /usr/lib/libglib-2.0.so.0(g_assertion_message+0x117) [0x7f39de279bc7]
        /usr/lib/libglib-2.0.so.0 [0x7f39de27a062]
        f-spot [0x42dbb8]
        f-spot [0x4e6229]
        f-spot [0x50849b]
        f-spot [0x508cd9]
        f-spot [0x5091d3]
        f-spot(mono_exception_from_name_two_strings+0xdd) [0x48c38d]
        f-spot(mono_runtime_init+0x13e) [0x48e64e]
        f-spot [0x4e31e5]
        f-spot(mono_main+0x341) [0x4169b1]
        /lib/libc.so.6(__libc_start_main+0xf4) [0x7f39dd83b1c4]
        f-spot(realloc+0x381) [0x416109]

Debug info from gdb:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f39dead77a0 (LWP 32191)]
[New Thread 0x7f39deae4950 (LWP 32192)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007f39dde0d5cb in read () from /lib/libpthread.so.0
  2 Thread 0x7f39deae4950 (LWP 32192) 0x00007f39dde0de81 in nanosleep ()
   from /lib/libpthread.so.0
  1 Thread 0x7f39dead77a0 (LWP 32191) 0x00007f39dde0d5cb in read ()
   from /lib/libpthread.so.0

Thread 2 (Thread 0x7f39deae4950 (LWP 32192)):
#0 0x00007f39dde0de81 in nanosleep () from /lib/libpthread.so.0
#1 0x00000000004b8f4f in ?? ()
#2 0x00007f39dde063f7 in start_thread () from /lib/libpthread.so.0
#3 0x00007f39dd8f4b2d in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f39dead77a0 (LWP 32191)):
#0 0x00007f39dde0d5cb in read () from /lib/libpthread.so.0
#1 0x00007f39de289a90 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f39de289f7e in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x00007f39de28a8df in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#4 0x00007f39de28ad98 in g_spawn_command_line_sync ()
   from /usr/lib/libglib-2.0.so.0
#5 0x000000000051bbf9 in ?? ()
#6 <signal handler called>
#7 0x00007f39dd84f095 in raise () from /lib/libc.so.6
#8 0x00007f39dd850af0 in abort () from /lib/libc.so.6
#9 0x00007f39de279bc7 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#10 0x00007f39de27a062 in g_assertion_message_expr ()
   from /usr/lib/libglib-2.0.so.0
#11 0x000000000042dbb8 in ?? ()
#12 0x00000000004e6229 in ?? ()
#13 0x000000000050849b in ?? ()
#14 0x0000000000508cd9 in ?? ()
#15 0x00000000005091d3 in ?? ()
#16 0x000000000048c38d in mono_exception_from_name_two_strings ()
#17 0x000000000048e64e in mono_runtime_init ()
#18 0x00000000004e31e5 in ?? ()
#19 0x00000000004169b1 in mono_main ()
#20 0x00007f39dd83b1c4 in __libc_start_main () from /lib/libc.so.6
#21 0x0000000000416109 in ?? ()
#22 0x00007fffe6b09308 in ?? ()
#23 0x0000000000000000 in ?? ()
#0 0x00007f39dde0d5cb in read () from /lib/libpthread.so.0

=================================================================
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.
=================================================================

Aborted