[Mono-bugs] [Bug 564256] abort in mono_arch_emit_prolog while JITting a verified method

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=564256

http://bugzilla.novell.com/show_bug.cgi?id=564256#c1


--- Comment #1 from Sebastien Pouliot <spouliot at novell.com> 2009-12-14 18:50:54 UTC ---
The same (condition wise) assert fails on x86 too.

ERROR:mini-x86.c:4706:mono_arch_emit_prolog: assertion failed: (cfg->code_len <
cfg->code_size)

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb747ab90 (LWP 5684)]
0xffffe430 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb7d60990 in raise () from /lib/libc.so.6
#2  0xb7d622c8 in abort () from /lib/libc.so.6
#3  0xb7f45f93 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#4  0xb7f4642d in g_assertion_message_expr () from /usr/lib/libglib-2.0.so.0
#5  0x0811cc61 in mono_arch_emit_prolog (cfg=0x8350518) at mini-x86.c:4706
#6  0x08061664 in mono_codegen (cfg=0x8350518) at mini.c:3004
#7  0x080633e9 in mini_method_compile (method=0x842076c, opts=64055807,
domain=0x34e70, run_cctors=0, compile_aot=0, parts=0) at mini.c:3819
#8  0x080d54e5 in compile_all_methods_thread_main (args=0xbfffeec8) at
driver.c:881
#9  0x0816b1d7 in start_wrapper (data=0x834a920) at threads.c:662
#10 0x08204776 in thread_start_routine (args=0x833030c) at wthreads.c:286
#11 0x0822224d in GC_start_routine (arg=0x35f20) at pthread_support.c:1390
#12 0xb7ec11b5 in start_thread () from /lib/libpthread.so.0
#13 0xb7e073ae in clone () from /lib/libc.so.6
(gdb) up 7
#7  0x080633e9 in mini_method_compile (method=0x842076c, opts=64055807,
domain=0x34e70, run_cctors=0, compile_aot=0, parts=0) at mini.c:3819
3819            mono_codegen (cfg);
(gdb) p method->name
$1 = 0xb7bb2167 "LookupComponentFromName"
(gdb) p method->klass->name
$2 = 0xb7ba843d "ManagedXamlLoader"
(gdb) p method->klass->name_space
$3 = 0xb7ba83b9 "Mono.Xaml"

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.