On Wed, 14 Jul 1999, Daniel Eischen wrote:
> > Can someone familiar with the new threads code tell me what is causing the > > following segmentation fault. Thanks. > > > > -Kip > > > > > > Program terminated with signal 11, Segmentation fault. > > #0 0x82fb15d in mutex_queue_enq (mutex=0x83c3a54, pthread=0x8594e00) > > at /usr/src/lib/libc_r/uthread/uthread_mutex.c:1281 > > 1281 > > PTHREAD_PRIOQ_INSERT_HEAD(pthread); > > (gdb) bt > > #0 0x82fb15d in mutex_queue_enq (mutex=0x83c3a54, pthread=0x8594e00) > > at /usr/src/lib/libc_r/uthread/uthread_mutex.c:1281 > > #1 0x82f9edd in pthread_mutex_lock (mutex=0x83c3ad4) > > at /usr/src/lib/libc_r/uthread/uthread_mutex.c:387 > > I take it you're running -stable without any mods to the threads > library, right? > > There are some bugs in libc_r in stable that have been fixed in > -current. I think the one that you've hit is an uninitialized > TAILQ_HEAD in a statically declared mutex (in localtime). It's > probably about time for a MFC. If someone wants to give me the > go-ahead, I can do it... > > In the mean time, you can grab libc_r/uthread/* from -current > and rebuild libc_r under -stable. Yes, I am running -stable. I did upgrade my libc_r a few weeks ago as a result of a problem with infinite recursion in write. When was this bug fixed? Thanks. -Kip > > Dan Eischen > eisc...@vigrid.com > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message