To support dynamic binding of "modules" (whole object files) the
symbol table must reflect the modules that the file was created from.
This is done by having a module table that has indexes and counts
into the merged tables for each module. The module structure that
these two entries refer to is described below. This exists only in a
dynamically linked shared library file. For executable and object
modules the file only contains one module so everything in the file
belongs to the module.
File offset to module table.
To support dynamic binding of "modules" (whole object files) the symbol table must reflect the modules that the file was created from. This is done by having a module table that has indexes and counts into the merged tables for each module. The module structure that these two entries refer to is described below. This exists only in a dynamically linked shared library file. For executable and object modules the file only contains one module so everything in the file belongs to the module.