Landau, Bracha wrote:
> As you suggested, I've upgraded to xenomai 2.2 rc3.
> I still see the same phenomenon.
> I'm attaching code that will reproduce the error.
> (When you ^c out of the main loop, the pthread_cleanup_pop is called, and
> the call to pthread_mutex_destroy returns 0x10.)
I did not make myself clear...
I did not meant that 2.2 rc3 would solve your issue, simply that it has
automatic per-process cleanup, so, it does not matter if your
application fail to destroy some condition variables, the condition
variable is destroyed automatically anyway. It is simpler for you to
work with this version as long as the bug you met is not solved.
As for the pthread_cleanup_push/pthread_cleanup_pop, it was meant to be
the solution if the EBUSY had been due to a thread blocked in a call to
pthread_cond_wait during the application cleanup.
I have a look at your code.
--
Gilles Chanteperdrix.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
