[Mono-bugs] [Bug 597072] abort in create_jit_info while JITting a verified method
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Mon Jul 19 16:00:22 EDT 2010
http://bugzilla.novell.com/show_bug.cgi?id=597072
http://bugzilla.novell.com/show_bug.cgi?id=597072#c1
--- Comment #1 from Sebastien Pouliot <spouliot at novell.com> 2010-07-19 20:00:20 UTC ---
Created an attachment (id=376942)
--> (http://bugzilla.novell.com/attachment.cgi?id=376942)
assembly causing the abort
newer test case on x86 opensuse 11.3
gdb --args mono --security=core-clr --compile-all bin/System.sigabrt.18669.dll
* Assertion at mini.c:3600, condition `tblock' not met
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb73deb70 (LWP 14133)]
0xffffe424 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb7e2d7ff in raise () from /lib/libc.so.6
#2 0xb7e2f140 in abort () from /lib/libc.so.6
#3 0x0827bc02 in monoeg_g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR,
format=0x829aa90 "* Assertion at %s:%d, condition `%s' not met\n", args=
0xb73ddfe4 "\207\252)\b\020\016") at goutput.c:134
#4 0x0827bc81 in monoeg_assertion_message (format=0x829aa90 "* Assertion at
%s:%d, condition `%s' not met\n") at goutput.c:154
#5 0x08060935 in create_jit_info (cfg=0x8637048,
method_to_compile="System.Net.Sockets.Socket:BeginReceive ()") at mini.c:3600
#6 0x080622c0 in mini_method_compile
(method="System.Net.Sockets.Socket:BeginReceive ()", opts=59861503,
domain=0x34e70, run_cctors=0, compile_aot=0,
parts=0) at mini.c:4460
#7 0x080e22a0 in compile_all_methods_thread_main (args=0xbfffee44) at
driver.c:878
#8 0x081e3fa2 in start_wrapper (data=0x8421aa0) at threads.c:747
#9 0x0826029f in thread_start_routine (args=0x840a7b4) at wthreads.c:285
#10 0x0828a401 in GC_start_routine (arg=0x5efc0) at pthread_support.c:1390
#11 0xb7f73b25 in start_thread () from /lib/libpthread.so.0
#12 0xb7ed546e in clone () from /lib/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.
More information about the mono-bugs
mailing list