From owner-freebsd-hackers  Wed Jul 14 11: 8:26 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP
	id EA46214C15; Wed, 14 Jul 1999 11:08:21 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id OAA25906;
	Wed, 14 Jul 1999 14:06:24 -0400 (EDT)
Date: Wed, 14 Jul 1999 14:06:24 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199907141806.OAA25906@pcnet1.pcnet.com>
To: hackers@FreeBSD.ORG, kip@lyris.com, stable@FreeBSD.ORG
Subject: Re: seg fault in mutex_queue_enq
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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.

Dan Eischen
eischen@vigrid.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message