[Mono-dev] (no subject)

Zoltan Varga vargaz at gmail.com
Sat Mar 22 16:00:34 UTC 2014 

Hi,

  This is already fixed in master.

          Zoltan


On Sat, Mar 22, 2014 at 11:02 AM, Rodrigo Kumpera <kumpera at gmail.com> wrote:

> We got a similar issue on our ARM devices.
>
> Alex, has this been fixed?
>
>
> On Thu, Mar 20, 2014 at 1:36 PM, Greg Young <gregoryyoung1 at gmail.com>wrote:
>
>> Just ran with redirected output this is the issue.
>>
>> AOT     [build] mcs.exe.so
>> Mono Ahead of Time compiler - compiling assembly
>> /home/greg/mono/mcs/class/lib/build/mcs.exe
>> * Assertion at method-to-ir.c:13337, condition `load_opcode !=
>> OP_LOADV_MEMBASE' not met
>>
>> Stacktrace:
>>
>>
>> Native stacktrace:
>>
>>         /home/greg/mono/mono/mini/mono() [0x4b8668]
>>         /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0) [0x2ab35a4eabb0]
>>         /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x2ab35a72ef77]
>>         /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x2ab35a7325e8]
>>         /home/greg/mono/mono/mini/mono() [0x639385]
>>         /home/greg/mono/mono/mini/mono() [0x6394c6]
>>         /home/greg/mono/mono/mini/mono() [0x47974a]
>>         /home/greg/mono/mono/mini/mono() [0x422d8a]
>>         /home/greg/mono/mono/mini/mono() [0x49dd42]
>>         /home/greg/mono/mono/mini/mono() [0x49fb6a]
>>
>> Debug info from gdb:
>>
>> [New LWP 6528]
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> 0x00002ab35a4ea757 in __libc_waitpid (pid=pid at entry=6529,
>> stat_loc=stat_loc at entry=0x7fffc0f9740c, options=options at entry=0) at
>> ../sysdeps/unix/sysv/linux/waitpid.c:40
>> 40      ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
>>   Id   Target Id         Frame
>>   2    Thread 0x2ab35d6b6700 (LWP 6528) "mono" sem_wait () at
>> ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
>> * 1    Thread 0x2ab359be6500 (LWP 6519) "mono" 0x00002ab35a4ea757 in
>> __libc_waitpid (pid=pid at entry=6529, stat_loc=stat_loc at entry=0x7fffc0f9740c,
>> options=options at entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40
>>
>> Thread 2 (Thread 0x2ab35d6b6700 (LWP 6528)):
>> #0  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
>> #1  0x000000000062fd57 in mono_sem_wait (sem=sem at entry=0x9834c0
>> <finalizer_sem>, alertable=alertable at entry=1) at mono-semaphore.c:119
>> #2  0x00000000005ad9ea in finalizer_thread (unused=unused at entry=0x0) at
>> gc.c:1073
>> #3  0x000000000058fe0b in start_wrapper_internal (data=0x1401fd0) at
>> threads.c:647
>> #4  start_wrapper (data=0x1401fd0) at threads.c:692
>> #5  0x000000000063482e in inner_start_thread (arg=0x7fffc0f98cd0) at
>> mono-threads-posix.c:94
>> #6  0x00002ab35a4e2f6e in start_thread (arg=0x2ab35d6b6700) at
>> pthread_create.c:311
>> #7  0x00002ab35a7f29cd in clone () at
>> ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
>>
>> Thread 1 (Thread 0x2ab359be6500 (LWP 6519)):
>> #0  0x00002ab35a4ea757 in __libc_waitpid (pid=pid at entry=6529,
>> stat_loc=stat_loc at entry=0x7fffc0f9740c, options=options at entry=0) at
>> ../sysdeps/unix/sysv/linux/waitpid.c:40
>> #1  0x00000000004b86f5 in mono_handle_native_sigsegv (signal=<optimized
>> out>, ctx=<optimized out>) at mini-exceptions.c:2305
>> #2  <signal handler called>
>> #3  0x00002ab35a72ef77 in __GI_raise (sig=sig at entry=6) at
>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
>> #4  0x00002ab35a7325e8 in __GI_abort () at abort.c:90
>> #5  0x0000000000639385 in monoeg_g_logv (log_domain=log_domain at entry=0x0,
>> log_level=log_level at entry=G_LOG_LEVEL_ERROR, format=format at entry=0x641ee8
>> "* Assertion at %s:%d, condition `%s' not met\n", args=args at entry=0x7fffc0f98338)
>> at goutput.c:175
>> #6  0x00000000006394c6 in monoeg_assertion_message (format=format at entry=0x641ee8
>> "* Assertion at %s:%d, condition `%s' not met\n") at goutput.c:195
>> #7  0x000000000047974a in mono_spill_global_vars (cfg=cfg at entry=0x5ff3e90,
>> need_local_opts=need_local_opts at entry=0x7fffc0f9877c) at
>> method-to-ir.c:13337
>> #8  0x0000000000422d8a in mini_method_compile (method=method at entry=0x5788730,
>> opts=<optimized out>, domain=<optimized out>, flags=flags at entry=JIT_FLAG_AOT,
>> parts=parts at entry=0) at mini.c:5610
>> #9  0x000000000049dd42 in compile_method (acfg=acfg at entry=0x1409f10,
>> method=0x5788730) at aot-compiler.c:6513
>> #10 0x000000000049fb6a in compile_method (method=<optimized out>,
>> acfg=0x1409f10) at aot-compiler.c:8426
>> #11 compile_methods (acfg=<optimized out>) at aot-compiler.c:8428
>> #12 mono_compile_assembly (ass=ass at entry=0x1404dd0, opts=opts at entry=370239999,
>> aot_options=aot_options at entry=0x7fffc0f9b31a
>> "bind-to-runtime-version,outfile=./../../class/lib/build//mcs.exe.so")
>> at aot-compiler.c:8835
>> #13 0x000000000048dadc in main_thread_handler (user_data=<synthetic
>> pointer>) at driver.c:1045
>> #14 mono_main (argc=6, argv=<optimized out>) at driver.c:2024
>> #15 0x00002ab35a719de5 in __libc_start_main (main=0x419800 <main>,
>> argc=6, ubp_av=0x7fffc0f990b8, init=<optimized out>, fini=<optimized out>,
>> rtld_fini=<optimized out>, stack_end=0x7fffc0f990a8) at libc-start.c:260
>> #16 0x0000000000419aac in _start ()
>>
>> =================================================================
>> Got a SIGABRT while executing native code. This usually indicates
>> a fatal error in the mono runtime or one of the native libraries
>> used by your application.
>> =================================================================
>>
>> Aborted (core dumped)
>>
>>
>>
>>
>>
>> On Thu, Mar 20, 2014 at 7:17 PM, Greg Young <gregoryyoung1 at gmail.com>wrote:
>>
>>> Didn't get one until the end and it was "unable to stat mcs" I thought I
>>> saw a SIGABORT somewhere along the way but it kept running.
>>>
>>>
>>>  On Thu, Mar 20, 2014 at 7:14 PM, "Andrés G. Aragoneses" <
>>> knocte at gmail.com> wrote:
>>>
>>>> On 20/03/14 18:08, Greg Young wrote:
>>>> > Before go searching for what happening and whether its something odd
>>>> > here can anyone build trunk right now? I can build 3.2.8 no problem
>>>>
>>>> Attaching the error message you get might help.
>>>>
>>>> (Also putting a subject in your email is not yet old-fashioned AFAIK)
>>>>
>>>> PS: I guess you mean 'master' (subversion is no more ;) )
>>>>
>>>> _______________________________________________
>>>> Mono-devel-list mailing list
>>>> Mono-devel-list at lists.ximian.com
>>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>>
>>>
>>>
>>>
>>> --
>>> Le doute n'est pas une condition agréable, mais la certitude est
>>> absurde.
>>>
>>
>>
>>
>> --
>> Le doute n'est pas une condition agréable, mais la certitude est absurde.
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140322/a3da9695/attachment-0001.html>

More information about the Mono-devel-list mailing list