X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<28233404.post@talk.nabble.com>
Date:	Tue, 13 Apr 2010 10:34:25 -0700 (PDT)
From:	gothrog <mvliguori AT whataremindsfor DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Usage of _exit(0) closes fd's of parent process
In-Reply-To:	<20100413021741.GA25597@roll>
MIME-Version:	1.0
References:	<20100411054851 DOT GA25578 AT roll> <20100413021741 DOT GA25597 AT roll>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I'm just taking a wild stab at this, but maybe the fork isn't working like
you think it should.  I know that when I use pthreads you have to specify
exactly how you expect it to split off and close.

I've heard of this type of behavior before and it all came down to how that
thread was spawned off originally.  Because it wasn't spawned properly, it
wasn't able to clean up right.

Good Luck.

Mike


-- 
View this message in context: http://old.nabble.com/Usage-of-_exit%280%29-closes-fd%27s-of-parent-process-tp28206735p28233404.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -