Shared libraries
Prev: Loading and overlays Next: Dynamic Linking and Loading
Problems
9.1
If you look in a /shlib directory on a Unix system with shared libraries, you’ll usually see three or four versions of each library with names like libc_s.2.0.1 and libc_s.3.0.0. Why not just have the most recent one?
9.2
In a stub library, why is it important to include all of the undefined globals for each routine, even if the undefined global refers to another routine in the shared library?
9.3
What difference would it make if a stub library were a single large executable with all of the library’s symbols as in COFF or Linux, or an actual library with separate modules?