[Mono-bugs] [Bug 462438] SIGSEGV while running tests/pinvoke2.exe on PowerPC

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=462438

User munroesj at us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462438#c2





--- Comment #2 from Steven Munroe <munroesj at us.ibm.com>  2008-12-24 11:16:44 MST ---
The sigsegv is is a result of class->generic_class big not null but an invalid
pointer (=0xffffffff). 

0x1015fa38 in mono_class_init (class=0x10381e48)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/metadata/class.c:3525
3525            if (class->generic_class && !class->generic_class->is_dynamic)
{

like 462016 it seems that this MonoClass has been clobbered or incorrectly
initialized.

The call stack up to  is also similar to 462016:

#0  0x1015fa38 in mono_class_init (class=0x10381e48)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/metadata/class.c:3525
#1  0x1011303c in mono_marshal_load_type_info (klass=0x10381e48)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/metadata/marshal.c:11349
#2  0x10113504 in mono_class_native_size (klass=0x10381e48, align=0xffc74238)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/metadata/marshal.c:11488
#3  0x1001bad8 in mono_allocate_stack_slots_full (cfg=0x10390900, backward=0,
    stack_size=0xffc742bc, stack_align=0xffc742c0)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/mini/mini.c:10364
#4  0x100e78a0 in mono_arch_allocate_vars (m=0x10390900)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/mini/mini-ppc.c:1185
#5  0x1005272c in mini_method_compile (method=0x1039c220,
    opts=<value optimized out>, domain=0xf7e6bee0,
    run_cctors=<value optimized out>, compile_aot=<value optimized out>,
    parts=0) at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/mini/mini.c:12744
#6  0x10053080 in mono_jit_compile_method (method=0x1039c220)
    at /home/sjmunroe/src/mono-ppc/mono-2.2/mono/mini/mini.c:13137


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