Re: [Xenomai-help] Getting calling task id inside RTDM driver

[Jan Kiszka <jan.kiszka@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Sean McGranaghan wrote:
> After posting I performed a two tests, first using an RTDM event and then using 
> a semaphore as described below. The synchronization worked in both cases, but I 
> think I have another problem. On exit my test application generates a 
> segmentation fault, but only occasionally. I do not get a stack dump in the 
> kernel log and the system does not seem to become unstable. I tried running my 
> test application under strace and gdb. In both cases I could not reproduce the 
> error. I am installing the latest version of Xenomai and adding debugging 
> options to the build. I will post when I know more.

mlockall? That's a typical thing to forget in your application (also
happens to me from time to time...), and it may or may not hit you with
a segfault one day.

> 
> Any suggestions on which Xenomai and kernel options to set for debugging?

The SVN contains some nice new debugging features for RTDM: catch
illegal contexts of rtdm_xxx-services and detect forgotten spinlocks
(via IRQs-on check) on return to the user. The latter already helped to
discover a bug in the xeno_16550A driver.

Moreover, if you are working on x86, the recent work on the kgdb
integration may be interesting as well. See related threads on the list.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]