From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Alex Plits <alex_plits@radwin.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Mixing Posix RT APIs and vxWorks APIs
Date: Tue, 5 Apr 2016 09:02:32 +0200 [thread overview]
Message-ID: <20160405070232.GI20399@hermes.click-hack.org> (raw)
In-Reply-To: <DB5PR06MB1287CCF7EAF55DA6F95ED4A68F9D0@DB5PR06MB1287.eurprd06.prod.outlook.com>
On Mon, Apr 04, 2016 at 01:42:11PM +0000, Alex Plits wrote:
> Hi,
>
> We are currently porting some of our vxWorks xenomai (copperplate) APIs we use in our application to
> Posix (cobalt I guess).
Well, if you do not know whether you are using Cobalt or Mercury, we
can not know it for you...
> We have started with the VxWorks "tasks" but it seems that we're getting strange behavior on
> The remaining VxWorks APIs when used from the POSIX generated tasks (threads is the right word in posix) e.g. MsqQRecv function gets segfault but when it is used From a VxWorks generated task it works fine.
> I understand from the comments in code it should work but I was wondering if there are known issues.
>
> We are using currently xenomai 3 rc-6 (I saw there were fixes in xenomai 3.0.2).
Could you send a self-contained, simplest possible test case which
causes the problem for you, that we can test on the latest Xenomai
release to see if the problem has not been already fixed?
Regards.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-04-05 7:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 13:42 [Xenomai] Mixing Posix RT APIs and vxWorks APIs Alex Plits
2016-04-05 7:02 ` Gilles Chanteperdrix [this message]
2016-04-07 5:56 ` Alex Plits
2016-04-07 17:56 ` Philippe Gerum
2016-04-25 10:03 ` Alex Plits
2016-04-25 10:38 ` Philippe Gerum
2016-04-25 10:41 ` Philippe Gerum
2016-04-25 11:42 ` Alex Plits
2016-04-26 8:10 ` Alex Plits
2016-05-02 19:17 ` Philippe Gerum
2016-05-03 13:06 ` Alex Plits
2016-05-11 6:59 ` Alex Plits
2016-05-23 9:14 ` 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=20160405070232.GI20399@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=alex_plits@radwin.com \
--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.