LDD(1)                    Linux Programmer's Manual                   LDD(1)

NAME         top

       ldd - print shared object dependencies

SYNOPSIS         top

       ldd [option]... file...

DESCRIPTION         top

       ldd prints the shared objects (shared libraries) required by each
       program or shared object specified on the command line.  An example
       of its use and output is the following:

       $ ldd /bin/ls
      => /lib64/ (0x00007f87e5459000)
      => /lib64/ (0x00007f87e5254000)
      => /lib64/ (0x00007f87e4e92000)
      => /lib64/ (0x00007f87e4c22000)
      => /lib64/ (0x00007f87e4a1e000)
               /lib64/ (0x00005574bf12e000)
      => /lib64/ (0x00007f87e4817000)
      => /lib64/ (0x00007f87e45fa000)

       In the usual case, ldd invokes the standard dynamic linker (see with the LD_TRACE_LOADED_OBJECTS environment variable set
       to 1.  This causes the dynamic linker to inspect the program's
       dynamic dependencies, and find (according to the rules described in and load the objects that satisfy those dependencies.  For
       each dependency, ldd displays the location of the matching object and
       the (hexadecimal) address at which it is loaded.  (The linux-vdso and
       ld-linux shared dependencies are special; see vdso(7) and

       Be aware that in some circumstances (e.g., where the program
       specifies an ELF interpreter other than, some versions
       of ldd may attempt to obtain the dependency information by attempting
       to directly execute the program (which may lead to the execution of
       whatever code is defined in the program's ELF interpreter, and
       perhaps to execution of the program itself).  Thus, you should never
       employ ldd on an untrusted executable, since this may result in the
       execution of arbitrary code.  A safer alternative when dealing with
       untrusted executables is:

           $ objdump -p /path/to/program | grep NEEDED

       Note, however, that this alternative shows only the direct
       dependencies of the executable, while ldd shows the entire dependency
       tree of the executable.

OPTIONS         top

              Print the version number of ldd.

       -v, --verbose
              Print all information, including, for example, symbol
              versioning information.

       -u, --unused
              Print unused direct dependencies.  (Since glibc 2.3.4.)

       -d, --data-relocs
              Perform relocations and report any missing objects (ELF only).

       -r, --function-relocs
              Perform relocations for both data objects and functions, and
              report any missing objects or functions (ELF only).

       --help Usage information.

BUGS         top

       ldd does not work on a.out shared libraries.

       ldd does not work with some extremely old a.out programs which were
       built before ldd support was added to the compiler releases.  If you
       use ldd on one of these programs, the program will attempt to run
       with argc = 0 and the results will be unpredictable.

SEE ALSO         top

       pldd(1), sprof(1),, ldconfig(8)

COLOPHON         top

       This page is part of release 4.12 of the Linux man-pages project.  A
       description of the project, information about reporting bugs, and the
       latest version of this page, can be found at

                                 2017-07-13                           LDD(1)

Pages that refer to this page: pldd(1)sprof(1)uselib(2)dl_iterate_phdr(3)dlopen(3)rtld-audit(7)vdso(7)ldconfig(8)