Re: Should we use _malloc_prefork and _malloc_postfork?

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

> I think we should go one step further than using them, and override
> fork() in libpthread so we can do similar things that the FreeBSD
> pthread fork does to make sure that it is safer (like blocking
> signals).

This strikes me as a very bad idea, because it's pretty much totally
non-extensible.  What happens when another library wants to override
fork similarly?

I'd much rather try to solve it more generally.  Perhaps atfork(), akin
to atexit()?  Or some linker magic so that each library wraps (in the
"ld --wrap" sense) the next's definition of (in this case) fork?

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B