From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Adrien LEMAITRE <adrien.lemaitre@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Problems with gdb and rt_task_delete
Date: Mon, 11 Jul 2011 14:12:29 +0200 [thread overview]
Message-ID: <4E1AE8AD.9060703@domain.hid> (raw)
In-Reply-To: <CALiYb9t21ijjNnpU4dVjfaKF3V_8XxGypUiiOkVROQdVyx-u8g@domain.hid>
On 07/11/2011 01:48 PM, Adrien LEMAITRE wrote:
> 2011/7/11 Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
>
>> On 07/11/2011 11:50 AM, Adrien LEMAITRE wrote:
>>> Hello,
>>>
>>> I have two problems. Just before explain my problems i would like to
>> clarify
>>> the context. This exercice is for student. In this exercice, they program
>> a
>>> WorkingTask (infini loop)
>>
>> That is the problem, there should not busy inifinite loops.
>> rt_task_sleep(100) asks for 100ns sleep, which is equivalent to not
>> sleeping at all.
>>
>> I seem to remember that I already told you this in answer to your
>> previous post.
>>
>
> yes and thanks you, i have a better understanding now. So ok if i would like
> to make an infini loop i must add a sleep of 5ms, otherwise i have problems.
> That is why i had needed rt_task_suspend(). And the problem with gdb is
> gone.
>
> But i don't see information of this in the wiki, could you show me exactly
> where i can find it?
>
You can probably sleep for shorter times than 5ms, 100us should be
enough. This is not documented, because it is an unwanted shortcoming,
which we hope to avoid one day, by implementing signals for xenomai,
working even for interrupting an infinite busy loop.
--
Gilles.
next prev parent reply other threads:[~2011-07-11 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 9:50 [Xenomai-help] Problems with gdb and rt_task_delete Adrien LEMAITRE
2011-07-11 11:05 ` Gilles Chanteperdrix
2011-07-11 11:48 ` Adrien LEMAITRE
2011-07-11 12:12 ` Gilles Chanteperdrix [this message]
2011-07-11 12:20 ` Adrien LEMAITRE
2011-07-11 13:25 ` 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=4E1AE8AD.9060703@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adrien.lemaitre@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.