From owner-freebsd-amd64@FreeBSD.ORG  Wed Feb 18 03:30:13 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 8AA6D16A4CE
	for <freebsd-amd64@freebsd.org>; Wed, 18 Feb 2004 03:30:13 -0800 (PST)
Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 13B8343D1D
	for <freebsd-amd64@freebsd.org>; Wed, 18 Feb 2004 03:30:13 -0800 (PST)
	(envelope-from adridg@cs.kun.nl)
Received: from odin.cs.kun.nl [131.174.33.33]  (helo=localhost)
	by pandora.cs.kun.nl (8.12.10/3.61) with ESMTP id i1IBUBCU021996
	for <freebsd-amd64@freebsd.org>; Wed, 18 Feb 2004 12:30:11 +0100 (MET)
From: Adriaan de Groot <adridg@cs.kun.nl>
To: freebsd-amd64@freebsd.org
Date: Wed, 18 Feb 2004 12:30:08 +0100
User-Agent: KMail/1.6.51
References: <Pine.GSO.4.44.0402171025520.15647-100000@wn4.sci.kun.nl>
	<200402171129.42641.peter@wemm.org>
In-Reply-To: <200402171129.42641.peter@wemm.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200402181230.11078.adridg@cs.kun.nl>
Subject: Re: The return of threading errors in ogg123
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Wed, 18 Feb 2004 11:30:13 -0000

On Tuesday 17 February 2004 20:29, you wrote:
> On Tuesday 17 February 2004 01:33 am, Adriaan de Groot wrote:
> > 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.
>
> I'm currently suspicious of the implementation of signal delivery and
> return handling for unrelated reasons.  It is possible that its also

libc_r seems solid as a rock; libpthread can play ok for a while but seems =
to=20
bail as soon as there is some load on the system. libpth doesn't work at al=
l,=20
missing a pthread_push_create symbol. Any gdb trickery I can use on the cor=
e=20
files to get more useful information out of them over the short bt?

=2D-=20
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@kde.org>
                     Would you like a freem?