Lesson plan

Dld (software)

Dld was a library package for the C programming language that performs dynamic link editing. Programs that use dld can add or remove compiled object code from a process anytime during its execution. Loading modules, searching libraries, resolving external references, and allocating storage for global and static data structures are all performed at run time. Dld supported various Unix platforms, having originally been developed for the VAX, Sun-3 and SPARCstation architectures. Its authors contrast its functionality with the dynamic linking that was at the time of its construction available in operating systems such as SunOS 4, System V.4, HP-UX and VMS: all of these operating systems had shared libraries, but did not allow programs to load additional libraries after startup. Dld offered this functionality without requiring changes to the OS or toolchain. Dld was a GNU package, but has been withdrawn because its functionality is available (through the dlopen API) in modern Unix-like operating systems.

Back to article

Article summary

Dld was a library package for the C programming language that performs dynamic link editing. Programs that use dld can add or remove compiled object code from a process anytime during its execution. Loading modules, searching libraries, resolving external references, and allocating storage for global and static data structures are all performed at run time. Dld supported various Unix platforms, having originally been developed for the VAX, Sun-3 and SPARCstation architectures. Its authors contrast its functionality with the dynamic linking that was at the time of its construction available in operating systems such as SunOS 4, System V.4, HP-UX and VMS: all of these operating systems had shared libraries, but did not allow programs to load additional libraries after startup. Dld offered this functionality without requiring changes to the OS or toolchain. Dld was a GNU package, but has been withdrawn because its functionality is available (through the dlopen API) in modern Unix-like operating systems.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.