Mike McCormack wrote:
Hi,
The loader seems to have a problem with extra backslashes in module pathnames.
If "c:\windows\system\ole32.dll" is loaded and unloaded, then "c:\windows\system\\ole32.dll" is loaded, there will be trouble, as the loader does not recognise these two as the same module, yet dlopen does.
Did you test what Windows does in that case ? (I also wonder where the double backslash comes from). A+
Hi Eric,
No, I didn't test what windows does, but something is amiss with what we're doing because Office 97 will not install with builtin ole32 without this fix. (I'm pretty sure it installs on windows :)
The double backslash comes from within the Office 97 installer itself.
Even if windows treats these as seperate modules, then we still have a problem, because dlopen works with unix pathes, and filenames differing by a backslash still have the same unix path.
Mike
Eric Pouech wrote:
Did you test what Windows does in that case ? (I also wonder where the double backslash comes from). A+
Even if windows treats these as seperate modules, then we still have a problem, because dlopen works with unix pathes, and filenames differing by a backslash still have the same unix path.
dlopen will almost certainly do a device/inode_number check on the open file, rather than any comparison of the names.
David
-
David Laight -
Eric Pouech -
Mike McCormack