Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Mon, 24 Jun 2002 16:11:04 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: suspicious code in dtable::dup2
Message-ID:	<20020624201104.GA29619@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3D176F08 DOT 6060800 AT hekimian DOT com>
Mime-Version:	1.0
In-Reply-To:	<3D176F08.6060800@hekimian.com>
User-Agent:	Mutt/1.3.23.1i

On Mon, Jun 24, 2002 at 03:12:08PM -0400, Joe Buehler wrote:
>Looking at dtable::dup2 in dtable.cc, it appears that it is possible
>to lock the fd list resource then exit the function without
>unlocking it.  Which presumably could cause a hang sometime later.

You're right.  I checked in a fix for this.

Thanks.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -