X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=NH4rhgsmDqH5hCSZoL47idaQCXeDNlX/OFreUQROjAU
	YXLvJrcVnhjlg2F0qh2tPgQ1LyXXfyRTspzzFhIGJyTQnI4ppR8zlDgMI+ORwikw
	KBT27XaqPx1lYKMDbMVgA1tXKem6a/SnQvkHd9k3PjtvhoVNEJvBeTNoci75zFlE
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=qjNomEg3884+OORCXuNwyqEYEUA=; b=mKU/DWWxuYiQADa+j
	Q/utZaMEEqofhITdlPenCbEZlEmQFuRG6qfazJ5wmhVCu+mm/F48IkyxmdT1g89s
	qvETBlm7zPA1iTe6fgcOcDUe9jEwnrHShZ0f4EpshvK2g9SFmEMQNqtKj2Y/h7qY
	frAJouEAbZ68RPrIZNjKkA4pbw=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-qg0-f52.google.com
X-Received:	by 10.140.128.73 with SMTP id 70mr31592087qha.75.1428507506648; Wed, 08 Apr 2015 08:38:26 -0700 (PDT)
Message-ID:	<55254B67.10209@gmail.com>
Date:	Wed, 08 Apr 2015 17:38:15 +0200
From:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Shared memory handling for mixed C/FORTRAN program
References:	<1999567694 DOT 2259208 DOT 1428493743005 DOT JavaMail DOT yahoo AT mail DOT yahoo DOT com>
In-Reply-To:	<1999567694.2259208.1428493743005.JavaMail.yahoo@mail.yahoo.com>
X-IsSubscribed:	yes

On 4/8/2015 1:49 PM, Christoph Weise wrote:
> I am porting to cygwin a program in FORTRAN/C that relies on C routines to create a shared memory region allowing various independent FORTRAN routines to share data. Program compiles and runs ok on Linux with g77/gcc compilers. I am compiling on cygwin 1.7.33-2(0.280/5/3)with gfortran/gcc (4.8.3).
>
> One C routine creates the shared memory section of a user-defined size. This seems to work just fine, although I had to add two lines to the sys/shm.h file:
>
>
> #define SHM_R        0400        /* or S_IRUGO from <linux/stat.h> */
> #define SHM_W        0200        /* or S_IWUGO from <linux/stat.h> */

don't do that.

Instead use S_IRUSR, S_IWUSR and companions:

http://pubs.opengroup.org/onlinepubs/7908799/xsh/sysstat.h.html


>
> The shm library functions seem to return reasonable info (page size and address, for removal of the shm section).
>
>
> Each FORTRAN routine then calls a C routine to find the shared memory, with a C routine returning pointers to two positions in the section intended for different kinds of data:
>
>
>
> #define PAGESIZE 1024
>
> int findshm(char**pptr,  /* Address of the parameter pointer */
>             float**cptr)  /* Address of the data pointer */
>
> ....calls to shm library functions ....
>
> shmaddr =0;
> p =shmat(shmid,shmaddr,(SHM_R |SHM_W));
> *pptr =p;
> *cptr =(float*)(p +PAGESIZE);
> return npages;
>
>
>
>
>
> The calling FORTRAN code looks like this:
>
>
>
> integer pptr,cptr
> integer npages
> npages =findshm(pptr,cptr)
>
> Although the total size of the created memory section npages is ok, the amount of memory following cptr is too small on cygwin (but not in Linux) and the program crashes for larger datasets with
>
> Program received signal SIGSEGV:Segmentationfault -invalid memory reference.
>
> Thinking it might have to do with the different underlying data types for the pointers (integer vs char/float) in the C versus FORTRAN code, I tried changing the type definitions of the pointers within the FORTRAN routines to
>
> byte pptr
> real*4 cptr
>
> and it all compiles and runs, but gives exactly the same runtime error, and doesn't explain why the program works in Linux.
>
> The pointer cptr is passed to FORTRAN subroutines as
>
> real cbuf(*)
>
> Not sure what I can do at this point (what to look out for, where to get help), so input appreciated.
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

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

- Raw text -