Date: Tue, 20 Oct 1998 22:41:12 -0400 (EDT) From: HighWind Software Information <info@highwind.com> To: eischen@vigrid.com Cc: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com, current@FreeBSD.ORG, lists@tar.com, tejblum@arc.hq.cti.ru Subject: Re: Another Serious libc_r problem Message-ID: <199810210241.WAA00469@highwind.com> In-Reply-To: <199810210200.WAA04708@pcnet1.pcnet.com> (message from Daniel Eischen on Tue, 20 Oct 1998 22:00:30 -0400 (EDT))
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, it seems that we need a method of disabling task scheduing while we enqueue the condition variable and call the thread kern scheduler. You should be able to do this by setting _thread_kern_in_sched = 1. Something like this (from pthread_cond_timedwait): Hmmm. If this is necessary here, wouldn't it be needed in other places in libc_r. Like uthread_mutex.c, uthread_join.c, uthread_fd.c Perhaps I'm confused. -- In the meantime, the earlier patch to uthread_cond.c seems to have worked. However, I'd really like to see libc_r become even more robust. I think it is time someone with commit-priv's gets involved to integrate this good work. We are happy to keep beating up the library and providing test programs that make it unhappy. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810210241.WAA00469>