On 01/17/2011 09:19 PM, Johannes Schlüter wrote: > I think it can be quite dangerous if you have extensions living shorter > than the PHP process. Not only might dlclose() cause some leaks but > there are a few extensions playing with function pointers or opcode > handlers which aren't properly reset so a following request might try to > jump to invalid memory.
dlclose()? I can assure you I'm not going to call dlclose() on each request shutdown. **** Yes, that means once an extension is loaded it'll stay till the death of this particular child process). But it does work here for the last 5 or 6 years this way and this is indeed what I want. **** TBH I'm not even sure dlclose() is called at all since I wasn't able to track this call down through all the handlers, destructors and so on in 5 min I spent on this.. > Additionally there's no restriction on this once safe_mode is gone, so > anybody could load any C extension - while that can be fixed by > advertising disable_function=dl That's right, disabling it is not a problem. -- Wbr, Antony Dovgal --- http://pinba.org - realtime statistics for PHP -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
