From owner-freebsd-hackers  Wed Jul 14 11:24:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from luna.lyris.net (luna.shelby.com [207.90.155.6])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6981A1542B; Wed, 14 Jul 1999 11:24:22 -0700 (PDT)
	(envelope-from kip@lyris.com)
Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4)
	id LAA22351; Wed, 14 Jul 1999 11:22:57 -0700 (PDT)
Received: from  (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 14 Jul 1999 11:22:57 -0700
Date: Wed, 14 Jul 1999 11:22:56 -0700 (PDT)
From: Kip Macy <kip@lyris.com>
X-Sender: kip@luna
To: Daniel Eischen <eischen@vigrid.com>
Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG
Subject: Re: seg fault in mutex_queue_enq
In-Reply-To: <199907141806.OAA25906@pcnet1.pcnet.com>
Message-ID: <Pine.SOL.4.05.9907141120280.21964-100000@luna>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-SMTP-HELO: luna
X-SMTP-MAIL-FROM: kip@lyris.com
X-SMTP-RCPT-TO: eischen@vigrid.com,hackers@FreeBSD.ORG,stable@FreeBSD.ORG
X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



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
> eischen@vigrid.com
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 
> 




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