This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: sysconf can call malloc?
- From: Roland McGrath <roland at redhat dot com>
- To: Ulrich Drepper <drepper at redhat dot com>
- Cc: "Boehm, Hans" <hans dot boehm at hp dot com>, libc-alpha at sources dot redhat dot com
- Date: Tue, 31 Jul 2007 13:46:02 -0700 (PDT)
- Subject: Re: sysconf can call malloc?
I don't disagree with your reasoning about the complexity of things sysconf
has to do. It seems entirely reasonable to me that applications and
libraries get the info they need from sysconf at startup time when it's
easy to be in a safe place.
But, POSIX.1 does list it as async-signal-safe. Any library writer, no
matter what kind of library they are writing, is completely reasonable to
expect it to be async-signal-safe given today's standard.
Are you working to change that specification?
Thanks,
Roland