The following reply was made to PR lib/30919; it has been noted by GNATS.

From: Rui Paulo <rpaulo@NetBSD.org>
To: gnats-bugs@netbsd.org
Cc: lib-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: lib/30919: current threads killing kmail
Date: Fri, 5 Aug 2005 17:50:57 +0100

 On 2005.08.05 15:33:01 +0000, Juan RP wrote:
 | The following reply was made to PR lib/30919; it has been noted by GNATS.
 | 
 | From: Juan RP <juan@xtrarom.org>
 | To: gnats-bugs@netbsd.org
 | Cc: mark@mcs.vuw.ac.nz
 | Subject: Re: lib/30919: current threads killing kmail
 | Date: Fri, 5 Aug 2005 17:31:36 +0200
 | 
 |  On Fri,  5 Aug 2005 12:02:00 +0000 (UTC)
 |  Mark Davies <mark@mcs.vuw.ac.nz> wrote:
 |  
 |  > >Description:
 |  > 	kmail has been working solidly for me on a NetBSD/i386 3.99.7
 |  > system of approx 1 July (and earlier versions). On updating the system
 |  > 	(kernel and userland) to one from yesterday (Aug 4) kmail now
 |  > repeatedly dies after displaying one or two messages with the
 |  > following error:
 |  > 
 |  > assertion "next != 0" failed: file
 |  > "/mnt/src/src/lib/libpthread/pthread_run.c", line 130, function
 |  > "pthread__next" *** KMail got signal 6 (Crashing)
 |  
 |  I had errors like this days ago with sylpheed, the problem was that
 |  libgpgerror was linked with librfuncs which has strerror_r(), and
 |  -current now has built into libc.
 |  
 |  Are you sure your librfuncs is using strerror_r() from libc? (it should)
 |  
 |  I'd try rebuilding all librfuncs dependent packages first (and
 |  librfuncs).
 
 PR#30660
 http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=30660
 
 		-- Rui Paulo