On 03/11/2013 11:35 AM, Petr Cervenka wrote:
> The problem with mutexes is still present. I'm really desperate now.
> Does anyone know, how the mutex could "stay locked" when every
> "acquire" is sooner or later followed by "release" and both functions
> always return 0 (success) code? Every advice is appreciated.
Could you provide us with a simple test case which would allow us to
reproduce the problem?
Other than that, you can try forcing the path through the kernel for
every mutex call, enable the I-pipe tracer, and trigger a trace as soon
as you detect that the mutex is not free after a release.
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
