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: Tue, 2 Mar 2004 12:11:55 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: problem about SEMAPHORE  at cygwin 1.5.7
Message-ID: <20040302111155.GF21589@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OF6D065114 DOT BD53B1C1-ON48256E4A DOT 00194F4A AT legend DOT com DOT cn>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF6D065114.BD53B1C1-ON48256E4A.00194F4A@legend.com.cn>
User-Agent: Mutt/1.4.2i

On Mar  1 12:36, xuzhd AT Lenovo DOT com wrote:
> (See attached file: lcctestsem.c)
> 
> problem about SEMAPHORE  at cygwin 1.5.7
> 
> cygwin 1.5.7
> cygserver as ipc server
> 
> a process has gotten semaphore using SEM_UNDO, when the  process aborts, it
> should release corresponding semaphore at Linux.But at Cygwin 1.5.7,1.5.4,
> 1.3.22, I cannot prove it. is it a bug to cygwin ? thank you

Yes, it's a bug in Cygserver.  Thanks for the testcase!  It helped to
track down the problem.  I've checked in a fix to Cygserver.  It will
show up in the next developers snapshot (http://cygwin.com/snapshots/).


Thanks again,
Corinna


-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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