Re: [PATCH] SEGV when loading module twice
We'd best move this to xemacs-beta before the wrath of the
xemacs-patches gods falls upon us.
wmperry(a)gnu.org (William M. Perry), on Sat, 09 Mar 2002 at 18:38:50
-0500 you wrote:
I have a bit of an issue here -- if this module has already been
loaded,
why are we calling dll_close()? This could seriously hose people on HP/UX
- their dlopen() implementation does not do any sort of reference counting,
so if you call dlclose() it will completely unload the module, so the first
instance will go boom (this is based off of experience with HP/UX 10.20 and
11.0).
Well, this is the right thing to do on systems with reference counting.
It sounds like we need to special case HP/UX in sysdll.c, then. I don't
have an HP/UX machine handy, unfortunately; I can attempt to come up
with a patch, but somebody else will have to test it for me. I wonder
if there is a way for configure to test for such behavior, just in case
there are other systems that act like that?
--
Jerry James