Manual browser: ldd(1)
|LDD(1)||General Commands Manual||LDD(1)|
NAMEldd — list dynamic object dependencies
|ldd||[-o] [-f format] program ...|
DESCRIPTIONldd displays all shared objects that are needed to run the given program. Contrary to nm(1), the list includes “indirect” dependencies that are the result of needed shared objects which themselves depend on yet other shared objects. Zero, one or two -f options may be given. The argument is a format string passed to rtld(1) and allows customization of ldd's output. The first format argument is used for library objects and defaults to “\t-l%o.%m => %p\n”. The second format argument is used for non-library objects and defaults to “\t%o => %p\n”.
These arguments are interpreted as format strings a la printf(3) to customize the trace output and allow ldd to be operated as a filter more conveniently. The following conversions can be used:
- The main program's name (also known as “__progname”).
- The value of the environment variable LD_TRACE_LOADED_OBJECTS_PROGNAME in a.out and the program name from the argument vector from elf.
- The library name.
- The library's major version number.
- The library's minor version number (a.out only, ignored in elf).
- The full pathname as determined by rtld's library search rules.
- The library's load address
Additionally, \n and \t are recognized and have their usual meaning.
The -o option is an alias for -f %a:-l%o.%m => %p\n, which makes ldd behave analogously to nm -o.
SEE ALSOld(1), ld.elf_so(1), nm(1), rtld(1)
HISTORYA ldd utility first appeared in SunOS 4.0, it appeared in its current form in NetBSD 0.9a.
BUGSThe a.out ldd actually runs the program it has been requested to analyze which in specially constructed environments can have security implications.
|September 7, 2009||NetBSD 7.0|