Hello Philippe,

> You will have to remove the printf() from the low prio task for the
> nucleus watchdog to detect the runaway situation, otherwise, your task
> would be considered as being under the control of the Linux scheduler
> until it issues a blocking Xenomai syscall (which it never does), and
> therefore escape the watchdog detection. That's the particular case I
> was talking about.
Meanwhile i got my sample code running:
When removing the printf it works fine.
So for me it looks like a problem when a task is switched to secondary
domain.
Is there a way to force a thread to switch back to primary domain?

Now i unsuccesfully tried to get a posix skin variant running.
(my real app is based on pthread)
Since i only can use signals to suspend a posix thread (correct me if
i'm wrong) i run in the same problem with the secondary domain.

Is there a way to switch back to primary domain in posix skin?

Do i have a chance to do this with pthread or do i have to rewrite my
code using rt_task* calls?

Thanks for your help, regards

Carsten
-- 
Dipl.-Ing. Carsten Spieß
Softwareentwicklung - Beratung - Schulung
Lauterlech 39d
D-86152 Augsburg
Tel.: +49(821)15 999 765
Fax.: +49(821)15 999 767
mailto://[EMAIL PROTECTED]
http://www.carsten-spiess.de





_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to