All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Roberto Finazzi <rfinaz@tin.it>, xenomai@xenomai.org
Subject: Re: [Xenomai] Heap binding error (EWOULDBLOCK)
Date: Tue, 17 Oct 2017 12:04:02 +0200	[thread overview]
Message-ID: <96045a73-a4c5-a441-ec74-31d03322b0d3@xenomai.org> (raw)
In-Reply-To: <1508232053.2272.23.camel@scrappix.utpvision.local>

On 10/17/2017 11:20 AM, Roberto Finazzi wrote:
> Hi,
> I'm porting an old Xenomai 2.5.6 application to the Cobalt 3.0.5.
> In the original application there were several heaps shared between many
> processes.
> Now I maintained the same structure but, when I tryed to bind an already
> created heap from another process, I had always the EWOULDBLOCK error.
> The names used in create and bind were the same. In the previous
> application the heap was created using H_SHARED but now is obsolete.
> 
> Just to test I created two simple programs with a shared semaphore and
> the behaviour is the same: the second program is blocked always on the
> rt_sem_bind even if the semaphore is already created.
> It seems like if the name of the shared resource is not registered
> properly.
> 
> Have you got some suggestions for me?
> 

--enable-pshared is required for sharing common resources between processes.


-- 
Philippe.


  reply	other threads:[~2017-10-17 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17  9:20 [Xenomai] Heap binding error (EWOULDBLOCK) Roberto Finazzi
2017-10-17 10:04 ` Philippe Gerum [this message]
2017-10-18  6:03   ` Roberto Finazzi
2017-10-18  9:02     ` Philippe Gerum
2017-10-18  9:55       ` Roberto Finazzi
2017-10-18 16:40         ` Philippe Gerum

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=96045a73-a4c5-a441-ec74-31d03322b0d3@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=rfinaz@tin.it \
    --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.