From: Eric Hodel Date: 2013-03-30T03:37:47+09:00 Subject: [ruby-core:53828] Re: Thread/fork issue --Apple-Mail-47C2895E-B27B-4C2D-A188-0DCBF47DA33F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Mar 29, 2013, at 10:16, Jason Gladish wrote:= > I've found an issue where calling fork inside a thread, and passing a bloc= k to the fork, causes the forked process to continue after the block I've created http://bugs.ruby-lang.org/issues/8185 from this email. PS: you can create issues directly at http://bugs.ruby-lang.org/projects/rub= y-trunk/issues/new= --Apple-Mail-47C2895E-B27B-4C2D-A188-0DCBF47DA33F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

On Mar 29, 2013, at 10:16, Jason Gladi= sh <jason@expectedbehavior.= com> wrote:

I've found a= n issue where calling fork inside a thread, and passing a block to the fork,= causes the forked process to continue after the block

I've created http://bugs.ruby-lang.org/issues/8185 from this email.

PS: you can create issues directly at http://bugs.ruby-lang.o= rg/projects/ruby-trunk/issues/new

= --Apple-Mail-47C2895E-B27B-4C2D-A188-0DCBF47DA33F--