Hi All, Thanks for your time and advice. I was investigating this so didn't want to reply earlier.
It turned out to be a bug in the application code :(. One of the events was getting ignored by the pool threads. Indeed process shared mutexes / cond variables works perfectly on 9.29. Fixed it last Friday. Regards, Sridhar On Tue, Aug 2, 2011 at 4:17 PM, Khem Raj <[email protected]> wrote: > > > On Aug 2, 2011, at 7:10 AM, Carmelo Amoroso <[email protected]> wrote: > > > On 1 August 2011 13:29, Sridhar Uravakonda <[email protected]> > wrote: > >> Hi All, > >> > >> I am using 0.9.29 uclibc on a MIPS platform. > >> > >> While testing a sample program with process shared mutexes and process > >> shared conditional variables (pthread_cond_wait, pthread_cond_broadcast, > >> pthread_mutex_lock, pthread_mutex_unlock) > >> > >> I see an issue when 3 threads from 3 different processes are working > >> together on the shared mtuex / cond variable. One of the threads gets > stuck > >> on the mutex even though I can see other two threads have unlocked it > >> successfully after their last usage. > > And preferably against master > >> > >> Does anyone know of any issues fixed on this? > >> > >> Regards, > >> Sridhar > > > > Hi, > > your scenario is not so clear... so are referrign to processes then > > threads then both. > > Please post a test case that is not working to allow us to debug it. > > > > Thanks, > > Carmelo > > > >> _______________________________________________ > >> uClibc mailing list > >> [email protected] > >> http://lists.busybox.net/mailman/listinfo/uclibc > >> > > _______________________________________________ > > uClibc mailing list > > [email protected] > > http://lists.busybox.net/mailman/listinfo/uclibc > _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
