This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

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: sysconf can call malloc?

From: Ulrich Drepper <drepper at redhat dot com>
To: "Boehm, Hans" <hans dot boehm at hp dot com>
Cc: libc-alpha at sources dot redhat dot com
Date: Tue, 31 Jul 2007 13:27:45 -0700
Subject: Re: sysconf can call malloc?
References: <BDA38860DCFD334EAEA905E44EE8E7EFDF29B0@G3W0067.americas.hpqcorp.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Boehm, Hans wrote:
> But this looks wrong to me for more serious reasons:  sysconf() is
> required to be async-signal-safe.

This is simply an unacceptable restriction.  Many of the problems values
sysconf has to compute are complex, requiring them all to be async-safe
is wrong.

I'm really tired of all those people who want to replace malloc and then
complain that the world is wrong if they run into problems.  If you want
to tinker with these lowlevel details it's you who has to resolve the
comflicts.

- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGr5tB2ijCOnn/RHQRAm1mAJ4xozhU0HKITlMAfTCs9nsiW0J2YACgjeVH
7Eha1pSHdmXogowq4wXezZk=
=gyVf
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: sysconf can call malloc?
  - From: Roland McGrath

References:
- sysconf can call malloc?
  - From: Boehm, Hans

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