Gerald Richter wrote:
> That's the same on NT. It seems to occur on all OSs, so it won't help
> anything to make the linker responsible, there are to much linkers... and I
> am not sure if the linker can know under all circumstances which libraries
> to unload.
Yes it can. Its main job is to keep track and control the dependencies
between libraries. It's just that sometimes thy don't do a particularly
good job of it ;-)
> I don't think we will convice the Apache people in the short term, that they
> shouldn't unload the libraries (also we can discuss it with them). The only
> practical solution I see, is the one to unload the libraries, as the patch
> already does. The thing left to do is to port it to other OS's (like NT)
> which does not have a function named dlclose (we need simply use another
> name). This solution will work and if the Apache people one time decide to
> not unload the modules, it won't hurt.
I think they should be persuaded - this is a very insiduous bug and
extremely hard to find.
> P.S. Does you get any feedback from your post to p5p about the unload
> function in Dynaloader?
No. Nothing meaningful.
Alan Burlison
