Hi, The above test appears to have started failing after https://github.com/mono/mono/commit/8f7b98b9b23dd5cc42011cff5c5c31b32ae1b55 6 (at least according to the jenkins log). What I’m seeing is that the obj pointer being passed to major_copy_or_mark_object_no_evacuation is 0x1000000000000:
Thread 2 (Thread 0x3fffaa7b910 (LWP 56738)): #0 0x000003fffd22df80 in waitpid () from /lib64/libpthread.so.0 #1 0x00000000800afd44 in mono_handle_native_sigsegv (signal=<optimized out>, ctx=<optimized out>, info=<optimized out>) at mini-exceptions.c:2243 #2 0x000000008001a3a2 in mono_sigsegv_signal_handler (_dummy=11, _info=0x3fffaa795e8, context=0x3fffaa79668) at mini-runtime.c:2462 #3 <signal handler called> #4 major_copy_or_mark_object_no_evacuation (queue=<optimized out>, obj=<optimized out>, ptr=<optimized out>) at sgen-marksweep-drain-gray-stack.h:133 #5 major_scan_object_no_evacuation (obj=<optimized out>, desc=<optimized out>, queue=0x803a8cc0 <gray_queue>) at sgen-scan-object.h:74 #6 0x0000000080231276 in drain_gray_stack_no_evacuation (ctx=...) at sgen-marksweep-drain-gray-stack.h:248 #7 drain_gray_stack (ctx=<error reading variable: value has been optimized out>) at sgen-marksweep.c:1223 #8 0x0000000080221476 in sgen_drain_gray_stack (max_objs=-1, ctx=<error reading variable: value has been optimized out>) at sgen-gc.c:552 #9 0x00000000802214e2 in finish_gray_stack (generation=1, ctx=...) at sgen-gc.c:1095 #10 0x000000008022366a in major_finish_collection (reason=0x80325f98 "user request", old_next_pin_slot=32, forced=1, scan_whole_nursery=<optimized out>) at sgen-gc.c:2017 #11 0x0000000080223c3a in major_do_collection (reason=0x80325f98 "user request", forced=1) at sgen-gc.c:2139 #12 0x0000000080223dc0 in sgen_perform_collection (requested_size=0, generation_to_collect=1, reason=0x80325f98 "user request", wait_to_finish=1) at sgen-gc.c:2379 #13 0x00000000802243d2 in sgen_gc_collect (generation=1) at sgen-gc.c:2800 #14 0x00000000801c784e in mono_domain_finalize (domain=0x803f4ee0, timeout=2000) at gc.c:379 #15 0x0000000080016c82 in mini_cleanup (domain=0x803f4ee0) at mini-runtime.c:3427 #16 0x0000000080142a62 in ves_icall_System_Environment_Exit (result=0) at icall.c:6001 I initially wondered about an endian issue with the forwarding bit but I can’t see anything in that particular push that has anything to do with this area of code. I am actively debugging the code now but wondered if anyone had seen anything that may cause this. Neale _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
