From: Tomoyuki Chikanaga Date: 2010-11-16T19:52:37+09:00 Subject: [ruby-core:33215] [Ruby 1.9-Bug#4009] Segfault with combination of threads and condition variables Issue #4009 has been updated by Tomoyuki Chikanaga. Hi I can reproduce similar SEGV under gdb with "ruby 1.9.3dev (2010-11-16 trunk 29789) [i686-linux]" Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1222669392 (LWP 14762)] 0x0813df46 in vm_call0 (th=0x9384238, recv=153972280, id=2512, argc=1, argv=0xb71f8948, me=0x92e8a68) at vm_eval.c:75 75 vm_push_frame(th, 0, VM_FRAME_MAGIC_CFUNC, (gdb) where #0 0x0813df46 in vm_call0 (th=0x9384238, recv=153972280, id=2512, argc=1, argv=0xb71f8948, me=0x92e8a68) at vm_eval.c:75 #1 0x0813e711 in check_funcall (recv=153972280, mid=2512, argc=1, argv=0xb71f8948) at vm_eval.c:290 #2 0x0813e73e in rb_check_funcall (recv=153972280, mid=2512, argc=1, argv=0xb71f8948) at vm_eval.c:296 #3 0x08059e05 in make_exception (argc=2, argv=0xb71f8944, isstr=1) at eval.c:552 #4 0x08059ebb in rb_make_exception (argc=2, argv=0xb71f8944) at eval.c:574 #5 0x081484e8 in rb_threadptr_raise (th=0x92a7568, argc=2, argv=0xb71f8944) at thread.c:1350 #6 0x0814c31a in rb_check_deadlock (vm=0x92a72e0) at thread.c:4465 #7 0x08147286 in thread_start_func_2 (th=0x9384238, stack_start=0xb71f8a78) at thread.c:516 #8 0x08146356 in thread_start_func_1 (th_ptr=0x9384238) at thread_pthread.c:361 #9 0x00666dd8 in start_thread () from /lib/tls/libpthread.so.0 #10 0x00f83d1a in clone () from /lib/tls/libc.so.6 th->cfp seemss pointed invalid address (gdb) p reg_cfp->sp Cannot access memory at address 0xb7278fe0 (gdb) p reg_cfp $9 = (rb_control_frame_t *) 0xb7278fdc (gdb) p *reg_cfp Cannot access memory at address 0xb7278fdc (gdb) p th->cfp $10 = (rb_control_frame_t *) 0xb7278fdc ---------------------------------------- http://redmine.ruby-lang.org/issues/show/4009 ---------------------------------------- http://redmine.ruby-lang.org