[Mono-devel-list] Mono segfaults with updated kernel?? 2.6.10

jrodman at mono-list.spamportal.net jrodman at mono-list.spamportal.net
Wed Jan 19 17:18:38 EST 2005

Hello Monoites,

It's possible I've made some kind of generic mistake with kernel
updates, but mono is segfaulting with a built 2.6.10 kernel.

This is on SuSE Linux Enterprise 9 on an AMD Opteron.  I have built
other kernels out of the SuSE sources which worked.  Using a vanilla
2.6.10, Mono segfaults.  Most 32-bit linux binaries on the distribution
seem to work fine.  Wine segfaults also, but later, and I distrust wine
as a canary due to its sentitive memory layout requirements.

It does not segfault on trivial invocation (no arguments produces nice
usage), but trivial invocation of the supplied mono binaries (eg.
/usr/bin/mono /usr/lib/mono/1.0/mcs.exe) does segfault.

Attempting to walk the unfortunately stripped executable shows it dying
in mono_domain_get () in /usr/lib/libmono.so.0

Program received signal SIGSEGV, Segmentation fault.
0x080de208 in ?? ()
(gdb) bt
#0  0x080de208 in ?? ()
#1  0x569080de in ?? ()
#2  0x080edf90 in ?? ()
#3  0x080effc8 in ?? ()
#4  0xffffced8 in ?? ()
#5  0x56908073 in ?? ()
#6  0x080edf90 in ?? ()
#7  0x080effc8 in ?? ()
#8  0xffffced8 in ?? ()
#9  0x5564e79f in mono_domain_get () from /usr/lib/libmono.so.0
Previous frame inner to this frame (corrupt stack?)

I'm basically looking for pointers here, not necessarily a solution.
I've never encountered binaries which go from working to crashing across
a kernel update within a major series, 2.6.5 -> 2.6.10



More information about the Mono-devel-list mailing list