From owner-freebsd-threads@FreeBSD.ORG Tue Jun 22 13:53:48 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E455316A4DC for ; Tue, 22 Jun 2004 13:53:48 +0000 (GMT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B8C343D5C for ; Tue, 22 Jun 2004 13:53:48 +0000 (GMT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i5MDrIon001152; Tue, 22 Jun 2004 09:53:18 -0400 (EDT) Date: Tue, 22 Jun 2004 09:53:18 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Chris Stenton In-Reply-To: <011f01c4578b$923d7b70$4b7ba8c0@gnome.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: pthread - fork - execv problem X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 13:53:49 -0000 On Mon, 21 Jun 2004, Chris Stenton wrote: > I am trying to help port over an app thats posix threaded. One thread uses > fork,dup2 and execv to start a child programme in this case an mp3 player. > However, under FreeBSD-5.2.1, the execv causes all the threads in the parent > process to be blocked until the child process returns. Is there a mechanism > to get around this. That shouldn't happen. What thread library? Sample program to demonstrate problem? -- Dan Eischen