Comment 19 for bug 237724

I am having the same issue with Jaunty Jackalope, log ahows as below:
Are there any fixes which are Jaunty specific rather than Hardy?

Thanks.

**
ERROR:mini-amd64.c:199:amd64_patch: assertion failed: (amd64_is_imm32 (disp))
Stacktrace:

Native stacktrace:

        /usr/bin/mono [0x429e65]
        /lib/libpthread.so.0 [0x7fec57c24080]
        /lib/libc.so.6(gsignal+0x35) [0x7fec57650fb5]
        /lib/libc.so.6(abort+0x183) [0x7fec57652bc3]
        /usr/lib/libglib-2.0.so.0(g_assertion_message+0x113) [0x7fec5829d4f3]
        /usr/lib/libglib-2.0.so.0 [0x7fec5829da82]
        /usr/bin/mono [0x437e98]
        /usr/bin/mono [0x540b9c]
        /usr/bin/mono [0x566640]
        /usr/bin/mono [0x5679f1]
        /usr/bin/mono [0x56812e]
        /usr/bin/mono [0x4bd42f]
        /usr/bin/mono(mono_runtime_init+0x14f) [0x4c05af]
        /usr/bin/mono [0x53cf3c]
        /usr/bin/mono(mono_main+0x311) [0x417831]
        /lib/libc.so.6(__libc_start_main+0xe6) [0x7fec5763c5a6]
        /usr/bin/mono [0x416ef9]

Debug info from gdb:

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

[Mon Jul 13 16:37:48 2009] [error] Failed to connect to mod-mono-server after several attempts to spawn the process.