[Mono-list] troubleshooting application lock up

Nikki Locke nikki at trumphurst.com
Thu May 18 08:11:49 EDT 2006

Miguel de Icaza wrote:
> Send a SIGQUIT signal to the Mono process, which will dump the stack 
> traces of all threads. 
> You need a modern Mono (at least 1.1.14) for this feature to work. 

I'm not the original poster, but I just installed mono 1.1.15, and tried 
that against an apparently hung process which should have had at least 20 
threads running (and was still showing its UI). The output was...

Full thread dump:

Which I found not very useful :-)

I tried sending signal SIGABRT, and got a core file. A stack backtrace 

#0  0x007427a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x009ad1ce in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
#2  0x009a9e37 in _L_mutex_lock_179 () from /lib/tls/libpthread.so.0
#3  0xbfffe90c in ?? ()
#4  0x081bd9b4 in ?? ()
#5  0x00000000 in ?? ()

but I'm none the wiser.

Any suggestions where to go from here?

Nikki Locke, Trumphurst Ltd.      PC & Unix consultancy & programming

More information about the Mono-list mailing list