Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 12 Aug 2004 12:44:09 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: cygserver shmat
Message-ID: <20040812104409.GA28756@cygbert.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin <cygwin@cygwin.com>
References: <1092302630.4368.3.camel@bma.sysgo.com> <20040812093246.GB24822@cygbert.vinschen.de> <1092305627.4368.10.camel@bma.sysgo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1092305627.4368.10.camel@bma.sysgo.com>
User-Agent: Mutt/1.4.2i

On Aug 12 12:13, bertrand marquis wrote:
> In fact i wasn't using the SHM_RNd flag.
> 
> In details here is what i do:
> 
> - get a shared segment of with size= SIZE (SIZE multiple of SHMLBA)
> - attach the segment without specifying address and storing the result
> in beginaddress
> - attach the segment again specifying the address: endposition=
> beginaddress + SIZE
> 
> without SHM_RND in the second shmat i've got the error : invalid
> argument
> 
> now that i specifie SHM_RND in the flag i have the error: value to large
> for defined type ....
> 
> any idea ?

Nope.  Not without knowing the actual values.  An strace output of
the affected calls would be good.  Even better, create a simple testcase
which allows to reproduce the behaviour.  Just the minimum of necessary
code.


Corinna

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