On 02/05/2014 12:08 PM, ali hagigat wrote:
On 2/3/14, Philippe Gerum <r...@xenomai.org> wrote:
On 02/01/2014 01:36 PM, ali hagigat wrote:
It seems that signal handler does not execute...
-------------- next part --------------
cat /proc/xenomai/sched
CPU PID CLASS PRI TIMEOUT TIMEBASE STAT NAME
0 0 idle -1 - master R ROOT/0
1 0 idle -1 - master R ROOT/1
2 0 idle -1 - master R ROOT/2
3 0 idle -1 - master R ROOT/3
0 0 rt 50 - master Df KTask1
0 0 rt 50 - master Df KTask2
dmesg
notify is successful...
This deprecated feature does not wake up the receiving task.
--
Philippe.
There are some warning messages complaining using the deprecated
function, "rt_task_create()" at compile.
but no warn message for rt_task_notify().
This function does not work at user space too.
Your application code does wrong assumptions on what
rt_task_notify/catch really does. So I'm unsure what "too" refers to in
your sentence, but as a matter of fact, your code can't work.
Besides, would you have cared for the warning at rt_task_create() and
refrained from using a dead interface from kernel space, you would not
have even considered using rt_task_notify() for sending signals to a
kernel-based native task in the first place.
Regarding the behavior of rt_task_notify() from user-space, you have to
provide evidence that you are properly using the interface, so that
people are not always investing time fixing your own bugs. You received
more than enough information in the previous conversations to do so.
FWIW, I had a quick look at the Xenomai code, and did not find anything
wrong.
--
Philippe.
_______________________________________________
Xenomai mailing list
Xenomai@xenomai.org
http://www.xenomai.org/mailman/listinfo/xenomai
