From owner-freebsd-threads@FreeBSD.ORG  Mon Jun 13 15:09:53 2005
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
X-Original-To: freebsd-threads@FreeBSD.org
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 8B7BD16A44C;
	Mon, 13 Jun 2005 15:09:53 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3760A43D48;
	Mon, 13 Jun 2005 15:09:53 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk)
	by mail.ticketswitch.com with esmtp (Exim 4.50 (FreeBSD))
	id 1DhqZU-000KKT-BF; Mon, 13 Jun 2005 16:09:52 +0100
Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim
	4.50 (FreeBSD)) id 1DhqZU-0000Jv-A8; Mon, 13 Jun 2005 16:09:52 +0100
To: bug-followup@FreeBSD.org, freebsd-threads@FreeBSD.org
In-Reply-To: <200505131740.j4DHe2gt043880@freefall.freebsd.org>
Message-Id: <E1DhqZU-0000Jv-A8@dilbert.firstcallgroup.co.uk>
From: Pete French <petefrench@ticketswitch.com>
Date: Mon, 13 Jun 2005 16:09:52 +0100
Cc: 
Subject: Re: threads/80992: abort() sometimes not caught by gdb depending on
	thread library
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2005 15:09:53 -0000


A bit more info - this problem seems to be related to the scope of the threads
as if I run the test program with LIBPTHREAD_SYSTEM_SCOPE defined then
the debugger catches the abort correctly and lets me trace the offending
method call.