From owner-freebsd-threads@FreeBSD.ORG Wed Jan 7 04:28:31 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D279C16A4CE for ; Wed, 7 Jan 2004 04:28:31 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C25843D53 for ; Wed, 7 Jan 2004 04:28:23 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i07CSKiw027472; Wed, 7 Jan 2004 07:28:20 -0500 (EST) Date: Wed, 7 Jan 2004 07:28:20 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Petri Helenius In-Reply-To: <3FFBECEC.8090709@he.iki.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-threads@freebsd.org Subject: Re: Release criteria for libkse -> libpthread switch? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2004 12:28:32 -0000 On Wed, 7 Jan 2004, Petri Helenius wrote: > Craig Rodrigues wrote: >=20 > >Hi, > > > >Dan Eischen has been periodically testing with ACE, which works quite we= ll > >with libkse. Are there other representative multithreaded applications= =20 > >which need to be tested? If so, which ones? > > > > =20 > > > I=B4ve been experimenting with running mysql-4.0 and it still seems to=20 > have issues > with signal handling. If the database is idle, shutdown works properly bu= t > if there is load on the database, shutting down never happens unless > forced with SIGKILL. >=20 > Unfortunately I haven=B4t had the time to debug this further, just=20 > periodically > updated both mysql and world to see if this would go away but it hasn=B4t= =2E >=20 > I=B4d be happy to provide more detail if somebody would point me to the= =20 > direction > where to look at. Send it a SIGINFO and look at the dumped thread states (/tmp/pthread.dump.x= xx).