This is the mail archive of the libc-hacker@sourceware.org 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] Don't call uname or getrlimit in libpthread init function


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

On 04/08/2010 04:16 PM, Andreas Schwab wrote:
> The last time I checked, uname was not in C99.

Neither is POSIX threads.  If you link with the DSO you're leaving ISO C
territory.

And moreover: when you define a function umask in your program (= the
executable) nothing bad will happen.  Preloading, as in this case, is
something completely different.

This is just another precedence for somebody doing stupid things and
expecting nothing to break.  It's just a bad idea to encourage this.  If
you replace a function then do it right and everything will work
correctly.  If the floodgates for these kinds of changes would be opened
we would have to add a whole lot of symbols to libc.so.  This doesn't
come without a cost.

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

iEYEARECAAYFAku+adcACgkQ2ijCOnn/RHQvZACggj8GMPsaR0Q/sVuyjMuGmVZI
fMcAmQGquepfyCfImc3ChYoFdJtsIcVs
=GG1m
-----END PGP SIGNATURE-----


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