http://bugzilla.novell.com/show_bug.cgi?id=625359
http://bugzilla.novell.com/show_bug.cgi?id=625359#c1 --- Comment #1 from Gonzalo Paniagua Javier <[email protected]> 2010-08-03 19:28:44 UTC --- I've been unable to reproduce this problem in a Core 2 Duo. In a Quad Core, I eventually got a SIGSEGV, but the stack trace is this one: Thread 2 (Thread 0x2760b70 (LWP 14720)): #0 0x00af1422 in __kernel_vsyscall () #1 0x00318f5b in read () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x080da06c in read (signal=11, ctx=0x275fd3c) at /usr/include/bits/unistd.h:45 #3 mono_handle_native_sigsegv (signal=11, ctx=0x275fd3c) at mini-exceptions.c:1931 #4 0x0805b61f in mono_sigsegv_signal_handler (_dummy=11, info=0x275fcbc, context=0x275fd3c) at mini.c:5359 #5 <signal handler called> #6 mono_install_handler_block_guard (thread=0x53958, ctx=0x275fe5c) at mini-exceptions.c:2137 #7 0x0811e86b in sigusr1_signal_handler (_dummy=35, info=0x275feac, context= 0x275ff2c) at mini-posix.c:208 #8 <signal handler called> #9 0x00af1422 in __kernel_vsyscall () #10 0x00318c7c in __lll_unlock_wake () from /lib/tls/i686/cmov/libpthread.so.0 #11 0x0031542b in _L_unlock_628 () from /lib/tls/i686/cmov/libpthread.so.0 #12 0x0031534a in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 #13 0x0815ca51 in thread_adjust_static_data (thread=0x321ff4) at threads.c:3644 #14 0x0815e79f in start_wrapper (data=0x0) at threads.c:697 #15 0x081e534f in thread_start_routine (args=0x8a1c3ac) at wthreads.c:285 #16 0x08216f59 in GC_start_routine (arg=0x5ea00) at pthread_support.c:1390 #17 0x0031196e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #18 0x001dda4e in clone () from /lib/tls/i686/cmov/libc.so.6 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
