From: Aliaksey Kandratsenka <redmine@...>
Date: 2010-04-06T12:22:21+09:00
Subject: [ruby-core:29276] [Bug #3100] Lockup in child after fork

Issue #3100 has been updated by Aliaksey Kandratsenka.


ruby_1_8_7@27173 and ruby_1_8@27224 still hang.

with 1.8.7 branch the backtrace is a bit different

(gdb) bt
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xf76d3b69 in __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:142
#2  0xf76d16f6 in pthread_cond_signal@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_signal.S:174
#3  0xf7728e6d in rb_thread_stop_timer () at eval.c:12357
#4  0xf75b38b6 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/i386/../fork.c:170
#5  0xf76d66f4 in __fork () at ../nptl/sysdeps/unix/sysv/linux/pt-fork.c:26
#6  0xf76f84d9 in establishShell (argc=1, argv=0xff9c80e0, self=4149235120) at pty.c:226

----------------------------------------
http://redmine.ruby-lang.org/issues/show/3100

----------------------------------------
http://redmine.ruby-lang.org