[Mono-bugs] [Bug 82833][Nor] Changed - assertion failed in mono_internal_hash_table_insert

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Sep 13 12:26:17 EDT 2007


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by george.barbarosie at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=82833

--- shadow/82833	2007-09-13 09:39:46.000000000 -0400
+++ shadow/82833.tmp.17385	2007-09-13 12:26:17.000000000 -0400
@@ -181,6 +181,56 @@
 __icall_wrapper_mono_thread_interruption_checkpoint
 
 ------- Additional Comments From mark.probst at gmail.com  2007-09-13 09:39 -------
 I can't reproduce this with Mono SVN on x86-64.  Could you run that
 test in gdb and produce a backtrace?  Also: Is this the only way you
 can reproduce the bug or do you have other test cases?
+
+------- Additional Comments From george.barbarosie at gmail.com  2007-09-13 12:26 -------
+I've updated to r85750, the bug still triggers on my setup.
+
+The only two methods I know that can trigger this bug are using xsp
+and running nant's common.generate-assemblyinfo. I am not
+knowledgeable enough in using .net to isolate the exact cause of this bug.
+
+Running mono directly under gdb does not work, the process seems to
+hang after loading the exe, before giving xsp2.exe a chance to open a
+port. I was able to attach gdb after starting xsp2.exe, but gdb loses
+connection with the program on SIGABRT or SIGTRAP (in case I try to
+place manual breaks in code), with a message such as:
+
+"Program terminated with signal SIGTRAP, Trace/breakpoint trap.
+The program no longer exists."
+
+I was able to get some more detailed backtrace information using
+addr2line on this backtrace:
+
+Native stacktrace:
+
+        /home/georgeb/devel/mono/mono/mini/mono [0x51bd3d]
+        /lib/libpthread.so.0 [0x2adff440fd70]
+        /lib/libc.so.6(gsignal+0x35) [0x2adff48cc665]
+        /lib/libc.so.6(abort+0x10e) [0x2adff48cda0e]
+        /usr/lib/libglib-2.0.so.0 [0x2adff409448c]
+        /usr/lib/libglib-2.0.so.0(g_log+0x83) [0x2adff4094513]
+        /usr/lib/libglib-2.0.so.0(g_assert_warning+0x76) [0x2adff4094596]
+        /home/georgeb/devel/mono/mono/mini/mono [0x4d207b]
+        /home/georgeb/devel/mono/mono/mini/mono [0x5091b8]
+        /home/georgeb/devel/mono/mono/mini/mono [0x43f9ee]
+        [0x40000139]
+
+$ addr2line -e /home/georgeb/devel/mono/mono/mini/mono -f -i 0x51bd3d
+0x4d207b 0x5091b8 0x43f9ee
+mono_handle_native_sigsegv
+/home/georgeb/devel/mono/mono/mini/mini-exceptions.c:1046
+mono_internal_hash_table_insert
+/home/georgeb/devel/mono/mono/utils/mono-internal-hash.c:97
+mono_jit_compile_method_inner
+/home/georgeb/devel/mono/mono/mini/mini.c:10989
+mono_jit_compile_method_with_opt
+/home/georgeb/devel/mono/mono/mini/mini.c:11058
+mono_jit_compile_method
+/home/georgeb/devel/mono/mono/mini/mini.c:11076
+mono_magic_trampoline
+/home/georgeb/devel/mono/mono/mini/mini-trampolines.c:72
+
+I hope this helps.


More information about the mono-bugs mailing list