Re: [Bug] dlopen() might cause deadlock

Wan-Teh Chang wrote:
> Ulrich Drepper wrote on 12/11/2003, 12:33 AM:
> 
>>No threaded program must use anything but
>>_exit or exec after fork.
> 
> 
> This is overly restrictive.  It is common for
> the child process to call dup2 and close after
> fork and before exec.

In nonthreaded programs, yes.  Paranoid programmers
hesitate to even call fork at all
after pthread_create has been called, don't they?
Or is that overly paranoid?
- Dan

p.s. just noticed the pthread_atfork function
http://www.opengroup.org/onlinepubs/007904975/functions/pthread_atfork.html
Whoever said there's nothing new under the sun must not
have been a software developer; I keep running into stuff
I should have known long ago every couple days...