Hello
I'm currently fighting with a problem in the pSOS+ skin.
This my system information:
[ 2.314676] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[ 2.416025] I-pipe: Domain Xenomai registered.
[ 2.418183] Xenomai: hal/i386 started.
[ 2.422780] Xenomai: scheduling class idle registered.
[ 2.424116] Xenomai: scheduling class rt registered.
[ 2.566737] Xenomai: real-time nucleus v2.5.4 (Sleep Walk) loaded.
[ 2.590628] Xenomai: starting native API services.
[ 2.604491] Xenomai: starting pSOS+ services.
[ 2.619941] HugeTLB registered 4 MB page size, pre-allocated 0 pages
This is a piece of testcode I have created:
check("tm_evevery",tm_evevery(4,3,&tmr_id),0);
check("tm_cancel",tm_cancel(tmr_id),0);
ev_rcvd = 0;
ret = ev_receive(4,EV_ANY|EV_WAIT,10,&ev_rcvd);
check("ev_receive",ret,ERR_TIMEOUT);
I just start a periodic timer that expires every 3 ticks and at expiry sends
event 4 to my task.
I want to check the cancel of the timer, so I cancel it and I would expect
not to receive any event.
What I observe is that this code is not working: I immediately receive the
event after starting the timer.
If I change the code like shown below (I added the ev_receive with the
NO_WAIT option after starting the timer), the code works fine.
check("tm_evevery",tm_evevery(4,3,&tmr_id),0);
ret = ev_receive(4,EV_ANY|EV_NOWAIT,0,&ev_rcvd);
check("tm_cancel",tm_cancel(tmr_id),0);
ev_rcvd = 0;
ret = ev_receive(4,EV_ANY|EV_WAIT,10,&ev_rcvd);
check("ev_receive",ret,ERR_TIMEOUT);
Now my question is: how do I investigate an issue like this? In other words,
which are the best tools since this code involves both user and kernel space
debugging.
Are there some trace tools available that are able to generate a kind of
sequence / trace of what is happing over time.
I also have other issues that are not consistently reproducible. For this
kind of problems trace tools would also be useful.
Thanks
Ronny
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
