[ECOS] problem with cyg_thread_release

Christoph Csebits christoph.csebits@frequentis.com
Thu Jan 8 17:56:00 GMT 2004

On Thu, Jan 08, 2004 at 06:38:47PM +0100, Andrew Lunn wrote:
> On Thu, Jan 08, 2004 at 04:42:24PM +0100, Christoph Csebits wrote:
> > FILEIO_MUTEX_LOCK returns with false, which is not handled and
> > further FILEIO_MUTEX_UNLOCK operates on a mutex, which the
> > thread does not own -> assertion.
> Handling all these cases would
> both add a lot of bloat which most people don't need and also be very
> error prone since its hard to test.

> I'd suggest you only use cyg_thread_release() on a thread when you
> know exactly where its blocked and can ensure it will do the right
> thing after being released.

Ok, its about the same we found out, when we discussed this.
Thanks for the answer, i was not sure about it.



Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

More information about the Ecos-discuss mailing list