From owner-freebsd-threads@FreeBSD.ORG Mon Oct 13 05:54:47 2003 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 1F7DF16A4B3; Mon, 13 Oct 2003 05:54:47 -0700 (PDT) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 162C843FBF; Mon, 13 Oct 2003 05:54:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from bluebottle.qubesoft.com (bluebottle.qubesoft.com [192.168.1.2]) by mail.qubesoft.com (8.12.9/8.12.9) with ESMTP id h9DCskFH038782; Mon, 13 Oct 2003 13:54:46 +0100 (BST) (envelope-from dfr@nlsystems.com) Received: from builder02.qubesoft.com (builder02.qubesoft.com [192.168.1.8]) h9DCsgbx037190; Mon, 13 Oct 2003 13:54:44 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1066049682.14360.17.camel@builder02.qubesoft.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 13 Oct 2003 13:54:42 +0100 Content-Transfer-Encoding: 7bit cc: threads@FreeBSD.org Subject: Re: GDB and libthr 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: Mon, 13 Oct 2003 12:54:47 -0000 On Mon, 2003-10-13 at 13:43, Daniel Eischen wrote: > On 13 Oct 2003, Doug Rabson wrote: > > > On Mon, 2003-10-13 at 12:54, Daniel Eischen wrote: > > > > > > I don't maintain libthr, but this looks OK to me. > > > > Sorry - I saw you comment on a similar message when I did a google > > search for gdb+libthr. Who would be a better person to send this to? It > > occurred to me that similar severe problems would occur with libthr if > > an application took a SIGSEGV, SIGBUS, SIGABORT or any other fatal > > unrecoverable signal while holding a mutex. > > Mike Makonnen (mtm) is the maintainer, but in theory posting to > threads@ with libthr problems (as well as libkse problems) should > also be sufficient. Thanks - I'll repost there.