man-pages/man1/ldd.1

176 lines
5.2 KiB
Groff
Raw Normal View History

2004-11-03 13:51:07 +00:00
.\" Copyright 1995-2000 David Engel (david@ods.com)
.\" Copyright 1995 Rickard E. Faith (faith@cs.unc.edu)
.\" Copyright 2000 Ben Collins (bcollins@debian.org)
.\" Redone for GLibc 2.2
.\" Copyright 2000 Jakub Jelinek (jakub@redhat.com)
.\" Corrected.
.\" and Copyright (C) 2012, 2016, Michael Kerrisk <mtk.manpages@gmail.com>
2013-03-10 09:29:51 +00:00
.\"
.\" %%%LICENSE_START(GPL_NOVERSION_ONELINE)
.\" Do not restrict distribution.
2004-11-03 13:51:07 +00:00
.\" May be distributed under the GNU General Public License
.\" %%%LICENSE_END
.\"
.TH LDD 1 2021-08-27 "" "Linux Programmer's Manual"
2004-11-03 13:51:07 +00:00
.SH NAME
ldd \- print shared object dependencies
2004-11-03 13:51:07 +00:00
.SH SYNOPSIS
.nf
.BR ldd " [\fIoption\fP]... \fIfile\fP..."
.fi
2004-11-03 13:51:07 +00:00
.SH DESCRIPTION
.B 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:
.PP
.in +4n
.EX
ldd.1: Fix example command Emanuele Torre via linux-man@: [ I was reading the man page for ldd(1)[1]; and I read this in the first paragraph of the DECRIPTION section: 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 (using sed(1) to trim leading white space for readability in this page) is the following: $ ldd /bin/ls | sed 's/^ */ /' linux-vdso.so.1 (0x00007ffcc3563000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f87e5459000) libcap.so.2 => /lib64/libcap.so.2 (0x00007f87e5254000) libc.so.6 => /lib64/libc.so.6 (0x00007f87e4e92000) libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f87e4c22000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f87e4a1e000) /lib64/ld-linux-x86-64.so.2 (0x00005574bf12e000) libattr.so.1 => /lib64/libattr.so.1 (0x00007f87e4817000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f87e45fa000) This is a little confusing though since that sed(1) command does not seem to work. (and also potentially misleading for someone who is trying figure out how to parse ldd(1)'s output.) ldd(1) prepends a TAB character (0x09) to each line, not spaces: $ ldd /bin/ls | xxd | head -1 00000000: 096c 696e 7578 2d76 6473 6f2e 736f 2e31 .linux-vdso.so.1 I read ldd(1)'s source code[2] (it is part of glibc) and it seems to be a bash script that tries to use different rtld programs ( ld.so(8) ) from an RTLDLIST. Those, on my system, are: * /usr/lib/ld-linux.so.2 * /usr/lib64/ld-linux-x86-64.so.2 * /usr/libx32/ld-linux-x32.so.2 And they all seem to also be part of glibc. I have tried to follow the git history of glibc to see when the switch from spaces to the TAB character occured, but, to me, it seems like glibc.git/elf/rtld.c has always used '\t'; at since 6a76c115150318eae5d02eca76f2fc03be7bd029[3] (358th commit since glibc started using the git repository repository - Nov 18th 1995): before that commit there are not any results for `git grep '\\t'` in the elf directory and I did not investigate further. Still, at the time of that commit, glibc did not seem to have an ldd(1) utility. Perhaps the man page is old and its original author was using and documenting an ldd(1) utility that was not part of glibc when he was writing it. Anyhow, since I think that sed(1) command will not work on any system that uses, at least, the most recent version of glibc (because lld(1) and the ld.so(8) programs it depends on are all part of glibc), I think that that example should be changed to avoid confusions. The output format of ldd(1) does not seem to be clearly defined, so I think this would be a good option: $ ldd /bin/ls | sed 's/^[[:space:]]*/ /' NB: ^\s* should also work on most GNU/Linux systems, but \s is non-standard or documented so I don not suggest using it in the man page. Another option could be to remove "the pipe to sed(1)" part and the note in parentheses that explains why it was used by the original author. Cheers. emanuele6 [1]: https://man7.org/linux/man-pages/man1/ldd.1.html [2]: https://sourceware.org/git/?p=glibc.git;a=blob;f=elf/ldd.bash.in;h=ba736464ac5e4a9390b1b6a39595035238250232;hb=5188a9d0265cc6f7235a8af1d31ab02e4a24853d [3]: https://sourceware.org/git/?p=glibc.git;a=commit;h=6a76c115150318eae5d02eca76f2fc03be7bd029 /////// $ uname -a Linux t420 5.10.54-1-lts #1 SMP Wed, 28 Jul 2021 15:05:20 +0000 x86_64 GNU/Linux $ pacman -Qo ldd /usr/bin/ldd is owned by glibc 2.33-5 $ pacman -Qo /usr/share/man/man1/ldd.1.gz /usr/share/man/man1/ldd.1.gz is owned by man-pages 5.12-2 $ pacman -Qo /usr/lib/ld-linux.so.2 /usr/lib/ld-linux.so.2 is owned by lib32-glibc 2.33-5 $ pacman -Qo /usr/lib64/ld-linux-x86-64.so.2 /usr/lib/ld-linux-x86-64.so.2 is owned by glibc 2.33-5 $ pacman -F /usr/libx32/ld-linux-x32.so.2 || echo not available on arch linux. not available on arch linux. ] Reported-by: EmanueleTorre <torreemanuele6@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2021-08-08 08:41:32 +00:00
$ \fBldd /bin/ls\fP
linux\-vdso.so.1 (0x00007ffcc3563000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f87e5459000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f87e5254000)
libc.so.6 => /lib64/libc.so.6 (0x00007f87e4e92000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f87e4c22000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f87e4a1e000)
/lib64/ld\-linux\-x86\-64.so.2 (0x00005574bf12e000)
libattr.so.1 => /lib64/libattr.so.1 (0x00007f87e4817000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f87e45fa000)
.EE
.in
.PP
In the usual case,
.B ldd
invokes the standard dynamic linker (see
.BR ld.so (8))
with the
.B 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
.BR ld.so (8))
and load the objects that satisfy those dependencies.
For each dependency,
.B ldd
displays the location of the matching object
and the (hexadecimal) address at which it is loaded.
(The
.I linux\-vdso
and
.I ld\-linux
shared dependencies are special; see
.BR vdso (7)
and
.BR ld.so (8).)
.\"
.SS Security
Be aware that in some circumstances
(e.g., where the program specifies an ELF interpreter other than
.IR ld\-linux.so ),
.\" The circumstances are where the program has an interpreter
.\" other than ld-linux.so. In this case, ldd tries to execute the
.\" program directly with LD_TRACE_LOADED_OBJECTS=1, with the
.\" result that the program interpreter gets control, and can do
.\" what it likes, or pass control to the program itself.
.\" Much more detail at
.\" http://www.catonmat.net/blog/ldd-arbitrary-code-execution/
some versions of
.B 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.
.\" Mainline glibc's ldd allows this possibility (the line
.\" try_trace "$file"
.\" in glibc 2.15, for example), but many distro versions of
.\" ldd seem to remove that code path from the script.
(In glibc versions before 2.27,
.\" glibc commit eedca9772e99c72ab4c3c34e43cc764250aa3e3c
the upstream
.B ldd
implementation did this for example,
although most distributions provided a modified version that did not.)
.PP
Thus, you should
.I never
employ
.B ldd
on an untrusted executable,
since this may result in the execution of arbitrary code.
A safer alternative when dealing with untrusted executables is:
.PP
.in +4n
.EX
$ \fBobjdump \-p /path/to/program | grep NEEDED\fP
.EE
.in
.PP
Note, however, that this alternative shows only the direct dependencies
of the executable, while
.B ldd
shows the entire dependency tree of the executable.
2004-11-03 13:51:07 +00:00
.SH OPTIONS
.TP
2005-10-04 12:49:58 +00:00
.B \-\-version
2004-11-03 13:51:07 +00:00
Print the version number of
.BR ldd .
.TP
.BR \-v ", " \-\-verbose
Print all information, including, for example,
symbol versioning information.
2004-11-03 13:51:07 +00:00
.TP
.BR \-u ", " \-\-unused
2006-07-12 10:41:40 +00:00
Print unused direct dependencies.
(Since glibc 2.3.4.)
2006-07-12 10:41:40 +00:00
.TP
.BR \-d ", " \-\-data\-relocs
2004-11-03 13:51:07 +00:00
Perform relocations and report any missing objects (ELF only).
.TP
.BR \-r ", " \-\-function\-relocs
2004-11-03 13:51:07 +00:00
Perform relocations for both data objects and functions, and
report any missing objects or functions (ELF only).
.TP
.B \-\-help
Usage information.
.\" .SH NOTES
.\" The standard version of
.\" .B ldd
.\" comes with glibc2.
.\" Libc5 came with an older version, still present
.\" on some systems.
.\" The long options are not supported by the libc5 version.
.\" On the other hand, the glibc2 version does not support
.\" .B \-V
.\" and only has the equivalent
.\" .BR \-\-version .
.\" .LP
.\" The libc5 version of this program will use the name of a library given
.\" on the command line as-is when it contains a \(aq/\(aq; otherwise it
.\" searches for the library in the standard locations.
.\" To run it
.\" on a shared library in the current directory, prefix the name with "./".
2004-11-03 13:51:07 +00:00
.SH BUGS
.B ldd
does not work on a.out shared libraries.
.PP
.B ldd
does not work with some extremely old a.out programs which were
built before
.B ldd
support was added to the compiler releases.
If you use
.B ldd
on one of these programs, the program will attempt to run with
.I argc
= 0 and the results will be unpredictable.
2004-11-03 13:51:07 +00:00
.\" .SH AUTHOR
.\" David Engel.
.\" Roland McGrath and Ulrich Drepper.
.SH SEE ALSO
.BR pldd (1),
.BR sprof (1),
2004-11-03 13:51:07 +00:00
.BR ld.so (8),
.BR ldconfig (8)