From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pthreads-win32-return-1121-listarch-pthreads-win32=sources.redhat.com@sourceware.org>
Received: (qmail 15844 invoked by alias); 29 Oct 2006 19:02:52 -0000
Received: (qmail 15836 invoked by uid 22791); 29 Oct 2006 19:02:52 -0000
X-Spam-Check-By: sourceware.org
Received: from outhub3.tibco.com (HELO outhub3.tibco.com) (63.100.100.166)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 29 Oct 2006 19:02:50 +0000
Received: from na-h-inhub2.tibco.com (na-h-inhub2 [10.106.132.33]) 	by outhub3.tibco.com (8.12.10/8.12.9) with ESMTP id k9TJ2h05028491; 	Sun, 29 Oct 2006 11:02:43 -0800 (PST)
Received: from NA-PA-VBE02.na.tibco.com (na-pa-be03.tibco.com [10.106.136.123]) 	by na-h-inhub2.tibco.com (8.13.6/8.13.6) with ESMTP id k9TJ2h3j010794; 	Sun, 29 Oct 2006 11:02:43 -0800 (PST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Memory leak with detached threads
Date: Sun, 29 Oct 2006 19:02:00 -0000
Message-ID: <5D819E730A717F47BC9B256CCE55297001C410D6@NA-PA-VBE02.na.tibco.com>
From: "Stephen Croall" <scroall@tibco.com>
To: "Giuliano Catrambone" <giuliano.catrambone@catrasoftware.it>
Cc: <pthreads-win32@sources.redhat.com>
X-IsSubscribed: yes
Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:pthreads-win32-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/pthreads-win32/>
List-Post: <mailto:pthreads-win32@sourceware.org>
List-Help: <mailto:pthreads-win32-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: pthreads-win32-owner@sourceware.org
X-SW-Source: 2006/txt/msg00056.txt.bz2

DOH!

Just realised that you are calling pthread_attr_setdetachstate().  You
could change to calling pthread_detach() to see if the memory leak still
happens.  We use this call a lot in our code and have no problems with
leaks.

Steve.