Re: [Bug] dlopen() might cause deadlock

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

Wan-Teh Chang wrote:

> This is overly restrictive.  It is common for
> the child process to call dup2 and close after
> fork and before exec.

If you want to call fork in an MT app something is wrong.  This never
has and never will be a good idea.  The only alternative to violating
the rules is to use posix_spawn which allows you to do have dup2 called.
 But don't try to argue in favor of relaxing the fork-related rules.
This just shows you have never thought about to implications.

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

iD8DBQE/2L2V2ijCOnn/RHQRAo0dAJ4jTX+F4+9Trv9fojXNaC5fNICgIgCgkUrU
urRsvQZUuv3Rswuabl+Y6bw=
=Y4zt
-----END PGP SIGNATURE-----