From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17189 invoked by alias); 30 Apr 2004 17:14:51 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 17171 invoked from network); 30 Apr 2004 17:14:51 -0000 Received: from unknown (HELO md.dent.med.uni-muenchen.de) (138.245.179.2) by sources.redhat.com with SMTP; 30 Apr 2004 17:14:51 -0000 Received: (qmail 2359 invoked by uid 211); 30 Apr 2004 17:14:50 -0000 Date: Fri, 30 Apr 2004 17:14:00 -0000 Message-ID: <20040430171450.2358.qmail@md.dent.med.uni-muenchen.de> From: Wolfram Gloger To: jakub@redhat.com CC: libc-hacker@sources.redhat.com In-reply-to: <20040429143129.GS5191@sunsite.ms.mff.cuni.cz> (message from Jakub Jelinek on Thu, 29 Apr 2004 16:31:30 +0200) Subject: Re: [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr} References: <20040429141901.GR5191@sunsite.ms.mff.cuni.cz> <20040429143129.GS5191@sunsite.ms.mff.cuni.cz> X-SW-Source: 2004-04/txt/msg00103.txt.bz2 Hello, > POSIX says on pthread_join: > > "For instance, after pthread_join() returns, any application-provided stack storage > could be reclaimed." Chapter and verse? This sounds rather vague, too. On comp.programming.threads, pthreads architect Dave Butenhof has claimed repeatedly that POSIX makes _no_ such guarantees, i.e. that strictly speaking you can _never_ free user-defined stack space.. Eg.: http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=ISO-8859-1&selm=3A797AB3.A57D43E9%40compaq.com Regards, Wolfram.