All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephan Adler" <stephan.adler@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Xenomai 2.4. and C++ (again)
Date: Wed, 3 Sep 2008 11:06:45 +0200	[thread overview]
Message-ID: <000801c90da4$63f46b10$2bdd4130$@adler@domain.hid> (raw)

Hi!

I am currently trying to run some C++ code as an Xenomai task. I wasn't aware that there are any problems with C++ until I found out today that some function calls in my C++ code break the real-time determinism of the task. Xenomai will not be able to interrupt the task although it should (as a higher-priority task should become active). The functions in question use the std::vector and std::string class.

After I became aware of that behavior I searched a little and found out that there is a C++ Wrapper class called Xeno-- and that the problems that occurred in my case seem to be well known.

Unfortunately I couldn't find any documentation what C++ calls are known to cause such a behavior. 

As I can not use the Xeno-- Wrapper for several reasons. I wonder if some user on this list has some experience with C++ and could provide a list of functions / practices to avoid to make C++ code work as expected. 

Some facts about the project:

- I use Xenomai 2.4.3

- Yes - I do call mlockall() before creating any task

- as far as I know no dynamic memory operations are done in the functions I use (I am not sure about every detail how std::vector / std::string work - but I don't explicitly generate new objects / delete them)

Thanks a lot
Stephan Adler





             reply	other threads:[~2008-09-03  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03  9:06 Stephan Adler [this message]
2008-09-03  9:28 ` [Xenomai-help] Xenomai 2.4. and C++ (again) 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='000801c90da4$63f46b10$2bdd4130$@adler@domain.hid' \
    --to=stephan.adler@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.