From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: roderik.wildenburg@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] how to build a Xenomai posix library ?
Date: Thu, 16 Oct 2008 14:41:36 +0200 [thread overview]
Message-ID: <48F73680.8020103@domain.hid> (raw)
In-Reply-To: <5D63919D95F87E4D9D34FF7748CE2C2A0155D80B@ARVMAIL1.mra.roland-man.biz>
roderik.wildenburg@domain.hid wrote:
>>>> roderik.wildenburg@domain.hid wrote:
>>> *shmfd = shm_open(LOGSHMNAME, oflags, 0);
>> a shm name should contain one slash at the beginning and no
>> other slash,
>> for best portability.
>
> As I expected, reducing the number of slashes to one does not change the behavior.
I never said it would.
>
>> If you want to create a shared memory, you should pass the
>> O_CREAT flag.
>
> As mentioned above, an other process creates the shared memory.
Is it also linked with xenomai posix skin?
> What I still don´t understand is, what influence the wrapper defines have on linking.
> With wrappers : aplication works fine. Without wrappers : application does not work !?
I would say that with wrappers, you are in fact using the vanilla linux
shared memory, by passing __wrap_shm_open, you really use xenomai posix
skin services.
If that is the case, when using the wrapped version, you should see the
shared memory appear under /dev/shm.
--
Gilles.
next prev parent reply other threads:[~2008-10-16 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:21 [Xenomai-help] how to build a Xenomai posix library ? roderik.wildenburg
2008-10-14 13:35 ` Gilles Chanteperdrix
2008-10-16 9:36 ` roderik.wildenburg
2008-10-16 9:48 ` Gilles Chanteperdrix
2008-10-16 10:14 ` roderik.wildenburg
2008-10-16 12:14 ` Gilles Chanteperdrix
2008-10-16 12:34 ` roderik.wildenburg
2008-10-16 12:41 ` Gilles Chanteperdrix [this message]
2008-10-17 9:58 ` [Xenomai-help] how to build a Xenomai posix library ? solved roderik.wildenburg
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=48F73680.8020103@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=roderik.wildenburg@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.