[Mono-dev] mono_aot_get_method, aot_mutex, and default_opt

[Gary Smithrud]

Bleep!  You are right.  dbx printed out that it was 0, but apparently  
it was confused.  I will try turning off aot tomorrow (I was  
performing a "make check" before installing, so I'll try installing  
anyway and turning off aot.)  Thanks.

On Sep 1, 2005, at 6:37 PM, Zoltan Varga wrote:

>                                     Hi,
>
>   The type of aot_mutex is CRITICAL_SECTION, which is a structure,  
> so it
> cannot be NULL. Try putting debug statements into  
> mono_aot_get_method and
> mono_aot_init to see which one is called first. Also, you can run  
> your program
> with -O=-aot to disable the AOT stuff altogether.
>
>                    Zoltan
>
> On 8/31/05, Gary Smithrud <gary.smithrud at haley.com> wrote:
>
>> I'm sorry if this is a repeat (we had a power issue and I'm not sure
>> that it got out), but I have not seen the original.  The issue is
>> that mono_aot_get_method is coredumping on Solaris 8 in the
>> LeaveCriticalSection because aot_mutex is NULL.  Default_opt is 0 and
>> so I believed that mono_aot_init was not being called (I believe that
>> that is the function name).  Unfortunately, when I commented out the
>> check for AOT and forced the call to mono_aot_init, the aot_mutex is
>> still NULL.  How do I get around this?
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>