From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Anders Norlander <anorland@hem2.passagen.se>
Cc: Chris Faylor <cgf@cygnus.com>,
cygwin@sourceware.cygnus.com,
Harold Weissfield <h_weissfield@hotmail.com>
Subject: Re: Memory Violation With Windres and Shared Data Segments
Date: Fri, 06 Aug 1999 10:47:00 -0000 [thread overview]
Message-ID: <199908061636.LAA05812@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <37AB1289.4EBCA966@hem2.passagen.se>
Anders Norlander <anorland@hem2.passagen.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@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Anders Norlander <anorland@hem2.passagen.se>
Cc: Chris Faylor <cgf@cygnus.com>,
cygwin@sourceware.cygnus.com,
Harold Weissfield <h_weissfield@hotmail.com>
Subject: Re: Memory Violation With Windres and Shared Data Segments
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <199908061636.LAA05812@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990831234900.iMahbOd9-xbaNn1rZynr5pCbWlqjABCpfRq61L_FLUw@z> (raw)
In-Reply-To: <37AB1289.4EBCA966@hem2.passagen.se>
Anders Norlander <anorland@hem2.passagen.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@sourceware.cygnus.com
next parent reply other threads:[~1999-08-06 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37AB1289.4EBCA966@hem2.passagen.se>
1999-08-06 10:47 ` Mumit Khan [this message]
1999-08-31 23:49 ` Mumit Khan
1999-08-09 10:55 Dirk Fieldhouse
1999-08-31 23:49 ` Dirk Fieldhouse
-- strict thread matches above, loose matches on Subject: below --
1999-08-06 20:25 Harold Weissfield
1999-08-06 21:10 ` Mumit Khan
1999-08-07 22:04 ` Mumit Khan
1999-08-31 23:49 ` Mumit Khan
1999-08-31 23:49 ` Mumit Khan
1999-08-31 23:49 ` Harold Weissfield
1999-08-06 7:58 Harold Weissfield
1999-08-06 8:51 ` Chris Faylor
1999-08-06 9:05 ` Mumit Khan
1999-08-31 23:49 ` Mumit Khan
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Harold Weissfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199908061636.LAA05812@mercury.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=anorland@hem2.passagen.se \
--cc=cgf@cygnus.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=h_weissfield@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).