From: Jan Kiszka <jan.kiszka@domain.hid>
To: DESVAGES Arnaud <desvages@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] real time task disapears... memory problem ?
Date: Wed, 06 Jun 2007 14:25:38 +0200 [thread overview]
Message-ID: <4666A7C2.5080206@domain.hid> (raw)
In-Reply-To: <000001c7a832$2f5b9230$0419dcc3@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
DESVAGES Arnaud wrote:
> Hello,
>
>
>
> I'm currently working on feedback scheduling. I have a set of tasks : an MPC
> controller, a feedback scheduler, and some disturbance tasks.
>
>
>
> To do feedback scheduling, I need to measure the execution time quite
> accurately, and xenomai can not measure the execution time spend in the
> secondary mode.
What kind of statistics would you precisely need? And where would you
need it, means where is your scheduler located, what API does it use?
> So I'm trying to stay in the primary mode. I had some calloc
> and free in one function that made me leave primary mode (for the MPC task).
>
>
>
> I tried to replace this by a rt_heap, and doing rt_heap_alloc in place of
> calloc, and I also tried to have static allocation.
>
>
>
>
>
> In both cases, my MPC task disappears when executing it! (nothing in
> /proc/xenomai/stat after the first try to execute it, but present during
> initialisation. and the other tasks are still here).
>
>
>
> I'm working on it for a few days now, and I can't find out what is wrong. I
> have tested to increase the maximum locked-in-memory size (in
> /etc/security/limits.conf). If I debug it with ddd, all is ok, array are
> well allocated...
>
>
>
> The strangest thing is that if I put a printf (this make a switch to
> secondary mode) saying that heap allocation was successful, everything works
> fine. So there is a function call that kills my task if I am in primary
> mode, and executes well if I am in secondary mode?
>
>
>
>
>
> Do you have any idea on where may be the mistake? Do you need some more
> information?
>
Primarily code. We need your code that demonstrates the weird behaviour.
If you patched Xenomai in any way, that patch would be required as well
of course.
BTW, did you already try to attach gdb to your disappearing process?
Maybe it can catch what makes it terminate.
>
>
>
>
> My config: Linux 2.6.17-x320 preempt
>
.config, Xenomai version, and I-pipe version can be helpful too.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-06-06 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:59 [Xenomai-help] real time task disapears... memory problem ? DESVAGES Arnaud
2007-06-06 12:25 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 16:23 desvages
2007-06-07 17:44 ` Jan Kiszka
[not found] ` <1753.194.254.210.7.1181246882.squirrel@domain.hid>
2007-06-08 15:19 ` Jan Kiszka
2007-06-09 16:06 ` desvages
2007-06-09 17:10 ` Jan Kiszka
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=4666A7C2.5080206@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=desvages@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.