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

Paolo Molaro lupus at ximian.com
Fri Jan 28 07:27:53 EST 2005

On 01/19/05 Joshua Rodman wrote:
> For those who might be interested, attached is the output of strace32.
> It seems like the process is dying during initial load/link.  This is
> running '/usr/bin/mono /usr/lib/mono/1.0/mcs.exe' with no arguments.
> Am I correct?  Is my distribution broken?
> open("/usr/local/NUnit/bin/mscorlib.dll", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
> open("/usr/lib/mscorlib.dll", O_RDONLY|O_LARGEFILE) = 4

This is most likely an old mscorlib.dll: in a correct default install
it should load mscorlib.dll from /usr/lib/mono/1.0/.
Try removing it.
The other option is that you might have and amd64 processor and the
new kernel enables the exec protection by default, so you'll need
to use mono svn for that fix (or wait for 1.0.6).
Or, since the stacktrace you posted starts from mono_domain_get(), it 
may be that tls access is broken on your system.


lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better

More information about the Mono-devel-list mailing list