From owner-freebsd-amd64@FreeBSD.ORG  Tue Feb 17 01:33:08 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8350016A4CE
	for <freebsd-amd64@freebsd.org>; Tue, 17 Feb 2004 01:33:08 -0800 (PST)
Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0D38443D2D
	for <freebsd-amd64@freebsd.org>; Tue, 17 Feb 2004 01:33:08 -0800 (PST)
	(envelope-from adridg@sci.kun.nl)
Received: from wn4.sci.kun.nl [131.174.8.3]  (helo=wn4.sci.kun.nl)
	by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1H9X7ni019302
	for <freebsd-amd64@freebsd.org>; Tue, 17 Feb 2004 10:33:07 +0100 (MET)
Date: Tue, 17 Feb 2004 10:33:07 +0100 (MET)
From: Adriaan de Groot <adridg@sci.kun.nl>
To: freebsd-amd64@freebsd.org
Message-ID: <Pine.GSO.4.44.0402171025520.15647-100000@wn4.sci.kun.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: The return of threading errors in ogg123
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: adridg@cs.kun.nl
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2004 09:33:08 -0000

Since a couple of weeks again, on -CURRENT, ogg123 has started bus
erroring and segfaulting again, just like it was back in november before
Peter's stack fixes. The "backtrace" is:

(gdb) bt
#0  0x0000000200f19320 in pthread_testcancel () from
/usr/lib/libpthread.so.1
#1  0x0000000200f10d68 in pthread_mutexattr_init ()
   from /usr/lib/libpthread.so.1
#2  0x0000000200f0f0ed in pthread_mutexattr_init ()
   from /usr/lib/libpthread.so.1
#3  0xd0d0d0d0d0d0d0d0 in ?? ()

so that's totally useless; I've just finished complete upgrade cycle with

FreeBSD beans.ebn.kun.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Feb 16
08:12:04 CET 2004
root@beans.ebn.kun.nl:/usr/obj/mnt/sys/CURRENT/src/sys/GENERIC  amd64

and done a portupgrade -acf, so things ought to be clean.

The problem doesn't trigger as often or as easily as it used to - I'm
trying libc_r now to see if that makes a difference, as well.