Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Thu, 3 Jun 2004 21:28:59 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: BUG:  shmget()  [was RE: shmget() not working(?)]
Message-ID: <20040603192859.GK7002@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <380-22004643181831593 AT hedden DOT us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <380-22004643181831593@hedden.us>
User-Agent: Mutt/1.4.2i

On Jun  3 14:18, Jerry D. Hedden wrote:
> shmget() is not able to 'find' an existing shared memory segment
> unless the 'flags' argument is set to '0'.  This is a bug.  If
> flags = 0666 (or at least compatible with the permissions set
> when the segment was created), it should still be able to find
> and use the segment.

Yes, it's a bug.  And I already found the cause, I used an internal flag
value which matches the upper permission bit.  Urgh.  This requires not
only another Cygserver, but also a new Cygwin DLL.

Thanks for the report,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader          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/