From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 14 15:43:16 2003 Return-Path: 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 6058516A4CE for ; Sun, 14 Dec 2003 15:43:16 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26FA043D09 for ; Sun, 14 Dec 2003 15:43:15 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost by pandora.cs.kun.nl id hBENhD1o016449 (8.12.10/3.58); Mon, 15 Dec 2003 00:43:13 +0100 (MET) From: Adriaan de Groot To: amd64 freebsd Date: Mon, 15 Dec 2003 00:43:10 +0100 User-Agent: KMail/1.5.94 References: <200312150029.00388.adridg@cs.kun.nl> In-Reply-To: <200312150029.00388.adridg@cs.kun.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200312150043.10380.adridg@cs.kun.nl> Subject: Re: End of pthread troubles in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 23:43:16 -0000 On Monday 15 December 2003 00:29, Adriaan de Groot wrote: > With the most-recent -CURRENT (well, from yesterday or so), and without > recompiling ogg123, the libmap.conf switch between libc_r and libkse works > fine, so I'd say the threading issues have been thrashed out. Thanks Peter. Guess I spoke too soon, since ogg123 cored after 9 tracks (instead of after 10 seconds), with console messages x: 2 x: 2 Dec 15 00:38:41 beans kernel: pid 768 (ogg123), uid 1001: exited on signal 11 (core dumped) (gdb) bt #0 0x0000000200eebb48 in pthread_testcancel () from /usr/lib/libkse.so.1 #1 0x0000000200ee3590 in pthread_mutexattr_init () from /usr/lib/libkse.so.1 #2 0x0000000200ee1915 in pthread_mutexattr_init () from /usr/lib/libkse.so.1 That's pretty much (testcancel) where it was crashing previously, (after the stack alignment fixes) as well.