You are not logged in.
Pages: 1
is it possible that because a library was not fully unloaded and replaced in same directory can cause errors when a new executable based on the library (or the same executable) is executed while the other executables are still loaded with their own "copy" of the library ?
does ldconfig solve this ? or do the libraries have to be first fully unloaded ? or does ldconfig has nothing to do with this because it only updates libdirs ?
Last edited by hopper (2009-05-27 22:44:04)
Offline
Pages: 1