From: Vit Ondruch <v.ondruch@...>
Date: 2011-11-23T17:21:07+09:00
Subject: [ruby-core:41241] [Backport87 - Bug #3100] Lockup in child after fork


Issue #3100 has been updated by Vit Ondruch.


Please can somebody take a look into this issue? Ruby 1.8.7-p352 are unfortunately still affected by this bug.
----------------------------------------
Bug #3100: Lockup in child after fork
http://redmine.ruby-lang.org/issues/3100

Author: Aliaksey Kandratsenka
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 
ruby -v: ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]


=begin
 I was using PTY.spawn and found a bug. I'm attaching a small testcase that at least on 2 my machines gives quite probable ruby process lockup in child.
 
 I'm also attaching gdb backtrace of locked up child. It can be seen that we're stuck in NTPL's low-level lock that protects timer thread condition variable. So it looks like I'm doing fork at 'right' time, when this condition is being signaled in parent.
 
 P.S. I'm categorizing it as core even though I can reproduce this only via PTY.spawn, 'cause pty.c looks very much innocent.
=end



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