Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199908061636.LAA05812@mercury.xraylith.wisc.edu>
To: Anders Norlander <anorland AT hem2 DOT passagen DOT se>
cc: Chris Faylor <cgf AT cygnus DOT com>, cygwin AT sourceware DOT cygnus DOT com,
        Harold Weissfield <h_weissfield AT hotmail DOT com>
Subject: Re: Memory Violation With Windres and Shared Data Segments 
In-Reply-To: Your message of "Fri, 06 Aug 1999 18:51:21 +0200."
             <37AB1289 DOT 4EBCA966 AT hem2 DOT passagen DOT se> 
Date: Fri, 06 Aug 1999 11:36:14 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Anders Norlander <anorland AT hem2 DOT passagen DOT se> writes:
> Just naming a section shared doesn't actually make it shared. There is a
> bit that
> has to be set in order to make a section shared. Unfortunately I don't
> remember
> more right now.

I believe the only difference is that it has the "SHARED" bit set in 
the section attributes, in addition to the usual initialized data,
read-write, etc flags.

Can someone send me a testcase so I can see if my local changes fix this
or not? If it's obvious already, I know nothing about these shared 
segments.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com