This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr}

From: Jakub Jelinek <jakub at redhat dot com>
To: Wolfram Gloger <wmglo at dent dot med dot uni-muenchen dot de>
Cc: libc-hacker at sources dot redhat dot com
Date: Sat, 1 May 2004 09:24:54 +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> <20040430171450.2358.qmail@md.dent.med.uni-muenchen.de> <20040430151958.GZ5191@sunsite.ms.mff.cuni.cz> <20040430180417.2588.qmail@md.dent.med.uni-muenchen.de>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Fri, Apr 30, 2004 at 06:04:17PM -0000, Wolfram Gloger wrote:
> Hi,
> 
> > It is in pthread_join's RATIONALE:
> > http://www.opengroup.org/onlinepubs/009695399/functions/pthread_join.html
> 
> Interesting.  AFAIC remember, this has changed from when I looked at
> it in 2001.  Although only in the "informative" section, I would
> actually welcome such a guarantee, and think we should make it
> possible to free application stacks after a return from
> pthread_join().

Actually, the yesterday released TC2 clarifies user defined stacks
and indeed a conforming application cannot free ever user defined stack
once it has been used successfully in some pthread_create or SIGEV_THREAD
notification. 2.9.8 is new in TC2:
http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html#tag_02_09_08

	Jakub

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]