From: Philippe Gerum <rpm@xenomai.org>
To: "Brian L." <bluczkie@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rt_task_delete behavior
Date: Sun, 21 May 2006 12:37:33 +0200 [thread overview]
Message-ID: <447042ED.5090806@domain.hid> (raw)
In-Reply-To: <6ee4c8380605202203w74a3c04j912d5e4e543f8433@domain.hid>
Brian L. wrote:
> No...
>
> hold on--self-destruction should never return. The calling task
> destroys itself then ceases to continue executing, right?
>
Yes.
> I suspect that late at night, three days ago, I confused 'not
> returning since the calling context is gone' with 'hanging'.
>
> If a thread's function (the one passed to rt_task_start) returns, is
> it cleaned up, or is it still neccesary to call rt_task_delete on it?
>
It's cleanup up automatically. This explains the output of
/proc/xenomai/sched below; the task has indeed gone away, and the only
remaining thread which keeps the process from exiting is likely the main
- non-Xenomai - one which is somehow paused or blocked.
> On 5/19/06, Philippe Gerum <rpm@xenomai.org> wrote:
>
>> Brian L. wrote:
>> > CPU PID PRI TIMEOUT STAT NAME
>> > 0 0 0 0 R ROOT
>> >
>>
>> Is this snapshot obtained while the application is still hanging?
>>
>> >
>> > On 5/18/06, Philippe Gerum <rpm@xenomai.org> wrote:
>> >
>> >> Brian L. wrote:
>> >> > I'm calling what amounts to rt_task_delete(rt_task_self()) and the
>> >> > task simply hangs, with this call never returning.
>> >> > rt_task_delete(NULL) behaves identically.
>> >> >
>> >> > What could cause this behavior? The problem is embedded within a
>> >> > nontrivial application, but it seems that it's not behaving
>> according
>> >> > to spec which says that the caller will only block when:
>> >> >
>> >> > 1. The target is in a "safe section"
>> >> >
>> >> > and
>> >> >
>> >> > 2. The caller is not the target
>> >> >
>> >> > Any ideas?
>> >> >
>> >>
>> >> Could you post the output of
>> >>
>> >> $ cat /proc/xenomai/sched
>> >>
>> >> TIA,
>> >>
>> >> > _______________________________________________
>> >> > Xenomai-help mailing list
>> >> > Xenomai-help@domain.hid
>> >> > https://mail.gna.org/listinfo/xenomai-help
>> >> >
>> >>
>> >>
>> >> --
>> >>
>> >> Philippe.
>> >>
>> >
>>
>>
>> --
>>
>> Philippe.
>>
>
--
Philippe.
prev parent reply other threads:[~2006-05-21 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 5:15 [Xenomai-help] rt_task_delete behavior Brian L.
2006-05-18 8:00 ` Philippe Gerum
2006-05-19 14:02 ` Brian L.
2006-05-19 14:46 ` Philippe Gerum
2006-05-21 5:03 ` Brian L.
2006-05-21 10:37 ` Philippe Gerum [this message]
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=447042ED.5090806@domain.hid \
--to=rpm@xenomai.org \
--cc=bluczkie@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.