Kolja Waschk wrote:
> Hi,
>
>> If not, recompile xenomai with --enable-debug, try and put a breakpoint
>> on the function xeno_sigshadow_handler. If you hit the breakpoint, try
>> and execute the function step by step, looking whether a pointer could
>
> The breakpoint isn't hit...
>
> With following setup:
>
> # continue to "_dl_get_ready_to_run" to be able to load symbols
> break *($pc - 0xC60 + 0x41B6)
> cont
>
> sharedlibrary
> break xeno_sigshadow_handler
> break main
>
> ... the output is as quoted below. Should xeno_sigshadow_handler be called as
> an
> immediate result of xeno_sigshadow_install? If I break on
> xeno_sigshadow_install,
> the fault doesn't occur and execution continues without problems to main()...
Well, I am not sure about this. A signal should be received as a result
of the call to __wrap_pthread_setschedparam, but the application should
receive it well before the handler is installed. So, this signal is
probably ignored by default, which somehow makes the thing work.
Anyway, what you can try to do is to mask the SIGSHADOW signal with
pthread_sigmask around the call to sigaction, in order to avoid whatever
race seems to happen with the libpthread library.
--
Gilles.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help