From owner-freebsd-hackers@FreeBSD.ORG  Wed Nov 29 00:07:23 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id F274D16A40F
	for <freebsd-hackers@freebsd.org>; Wed, 29 Nov 2006 00:07:22 +0000 (UTC)
	(envelope-from youshi10@u.washington.edu)
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu
	[140.142.32.134])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5190F43CA0
	for <freebsd-hackers@freebsd.org>; Wed, 29 Nov 2006 00:07:17 +0000 (GMT)
	(envelope-from youshi10@u.washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141])
	by mxout1.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP
	id kAT07MCk016538
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <freebsd-hackers@freebsd.org>; Tue, 28 Nov 2006 16:07:22 -0800
X-Auth-Received: from [128.208.1.159] (fubar.cs.washington.edu [128.208.1.159])
	(authenticated authid=youshi10)
	by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id
	kAT07LFC018791
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <freebsd-hackers@freebsd.org>; Tue, 28 Nov 2006 16:07:21 -0800
Message-ID: <456CCF39.9090808@u.washington.edu>
Date: Tue, 28 Nov 2006 16:07:21 -0800
From: Garrett Cooper <youshi10@u.washington.edu>
User-Agent: Thunderbird 1.5.0.8 (X11/20061108)
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
References: <456CAB12.9070507@u.washington.edu>
	<200611282302.08439.pieter@degoeje.nl>
	<456CBB09.10804@u.washington.edu>
	<200611290000.37322.pieter@degoeje.nl>
In-Reply-To: <200611290000.37322.pieter@degoeje.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055,
	Antispam-Data: 2006.11.28.155432
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0'
Subject: Re: pthreads : questions about concurrency and lifetime
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2006 00:07:23 -0000

Pieter de Goeje wrote:
> On Tuesday 28 November 2006 23:41, Garrett Cooper wrote:
>   
>> So that means no, after a function's definition is reached the
>> thread/resources stay in a semi-'alive' (maybe 'zombified') state?, or
>> does the kernel cleanup / reclaim all of the resources tied up with the
>> thread?
>> -Garrett
>>     
> If you detach the thread, it will properly clean up after it self, after the 
> thread has finished running.
>
> -- Pieter
>   
Awesome; that's the answer I was looking for.
Thanks again!
-Garrett