This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Adding reentrancy information to safety notes?
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Rich Felker <dalias at libc dot org>, Michael Kerrisk <mtk dot manpages at gmail dot com>, Peng Haitao <penght at cn dot fujitsu dot com>, "linux-man\ at vger dot kernel dot org" <linux-man at vger dot kernel dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 01 Jan 2015 05:05:14 -0200
- Subject: Re: Adding reentrancy information to safety notes?
- Authentication-results: sourceware.org; auth=none
- References: <54A2C8A6 dot 9050100 at redhat dot com> <ork318eoj4 dot fsf at livre dot home> <20141230230529 dot GT4574 at brightrain dot aerifal dot cx> <orfvbwegqg dot fsf at livre dot home> <54A377B8 dot 60802 at redhat dot com> <ortx0cdv3c dot fsf at livre dot home> <54A41595 dot 4010007 at redhat dot com>
On Dec 31, 2014, "Carlos O'Donell" <carlos@redhat.com> wrote:
> I did not know malloc was required to be AS-safe for POSIX compliance.
Ugh. Sorry, my bad, it's not. malloc's AS-safety goal seems to have
jumped from "desirable" to "mandatory" in my mind :-(
> See: http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html
> 2.4.3 Signal Actions.
> The list of functions does not list malloc.
Beware, that's a very old version of POSIX that you referenced above.
What led me to realize it was the use of the term "reentrant" there ;-)
Anyway, the corresponding table in current POSIX fails to list malloc as
AS-Safe just the same ;-)
> My pleasure. A list of examples helps not just you but future readers.
*nod*
Thanks, and happy GNU year to all!
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer