From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: shmat() ... is it a bug?
Date: Fri, 29 Aug 2003 00:48:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106211849808996@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106211685507764@msgid-missing>
>>>>> On Thu, 28 Aug 2003 17:04:10 -0700, Umut Aymakoglu <umuta@us.ibm.com> said:
Umut> Below ,I have 2 small programs which shows a problem in
Umut> shmat() when the executable linked with the curses
Umut> library(libncurses). Has anybody seen something like this?
Umut> a.c --> allocates a shared memory segment and attaches.
Umut> b.c --> attaching the allocated shared memory segment using the address
Umut> from a.c
The bug is in the program: you can't assume that a fixed virtual
address is available for mapping. When you link against -lncurses, it
happens to get loaded at the same address as "a" mapped the shared
memory segment. Obviously, you can't have the shared memory segment
and libncurses mapped at the same address, hence the failure.
--david
prev parent reply other threads:[~2003-08-29 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 0:04 shmat() ... is it a bug? Umut Aymakoglu
2003-08-29 0:48 ` David Mosberger [this message]
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=marc-linux-ia64-106211849808996@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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