From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jochen Behnke <JK.Behnke@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] App with pthreads using rt_task_shadow locks up
Date: Tue, 13 Mar 2007 19:12:27 +0100 [thread overview]
Message-ID: <45F6E98B.4040803@domain.hid> (raw)
In-Reply-To: <448721993@domain.hid>
Jochen Behnke wrote:
> Hello Gilles,
>
> thanks for your response.
> At the moment I try to cut down my application to the minimum.
> I also will install the latest version of the xenomai 2.2.x branch (2.2.5) and check whether I can reproduce the fault. As I noticed that some functions have been changed (rt_mutex_lock/unlock no longer exist in Xenomai 2.3.x, they obviously have been renamed for some reason) I would rather stick to the 2.2.x branch. Is that reasonable in your opinion ?
> Will the 2.2.x branch be maintained in the future ?
>
> Thanks again.
>
> Jochen
Please do not forget to CC the list.
rt_mutex_lock/rt_mutex_unlock were renamed
rt_mutex_acquire/rt_mutex_release to avoid a conflict, as documented in
API.CHANGES
Please try with Xenomai 2.3.0, or better with trunk. The aim of this
check is for us to avoid chasing bugs that were already solved. For
example if you are using fork() in your application, only I-pipe patches
in the trunk will solve your problem.
--
Gilles Chanteperdrix
next parent reply other threads:[~2007-03-13 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <448721993@domain.hid>
2007-03-13 18:12 ` Gilles Chanteperdrix [this message]
2007-03-16 7:12 [Xenomai-help] App with pthreads using rt_task_shadow locks up Jochen Behnke
-- strict thread matches above, loose matches on Subject: below --
2007-03-15 18:34 Jochen Behnke
2007-03-15 18:51 ` Philippe Gerum
2007-03-15 16:17 Jochen Behnke
2007-03-15 16:47 ` Philippe Gerum
2007-03-13 19:03 Jochen Behnke
2007-03-12 16:02 Jochen Behnke
2007-03-12 16:09 ` Gilles Chanteperdrix
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=45F6E98B.4040803@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=JK.Behnke@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.