Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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, 12 Aug 2004 12:44:09 +0200 From: Corinna Vinschen To: cygwin Subject: Re: cygserver shmat Message-ID: <20040812104409.GA28756@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin References: <1092302630 DOT 4368 DOT 3 DOT camel AT bma DOT sysgo DOT com> <20040812093246 DOT GB24822 AT cygbert DOT vinschen DOT de> <1092305627 DOT 4368 DOT 10 DOT camel AT bma DOT sysgo DOT 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 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/