pldd - display dynamic shared objects linked into a process
Contents
Bugs
From glibc 2.19 to glibc 2.29, pldd was broken: it just hung when executed. This problem was fixed in
glibc 2.30, and the fix has been backported to earlier glibc versions in some distributions.
Description
The pldd command displays a list of the dynamic shared objects (DSOs) that are linked into the process
with the specified process ID (PID). The list includes the libraries that have been dynamically loaded
using dlopen(3).
Examples
$ echo$$ # Display PID of shell
1143
$ pldd$$ # Display DSOs linked into the shell
1143: /usr/bin/bash
linux-vdso.so.1
/lib64/libtinfo.so.5
/lib64/libdl.so.2
/lib64/libc.so.6
/lib64/ld-linux-x86-64.so.2
/lib64/libnss_files.so.2
Exit Status
On success, pldd exits with the status 0. If the specified process does not exist, the user does not
have permission to access its dynamic shared object list, or no command-line arguments are supplied, pldd
exists with a status of 1. If given an invalid option, it exits with the status 64.
History
glibc 2.15.
Name
pldd - display dynamic shared objects linked into a process
Notes
The command
lsof -p PID
also shows output that includes the dynamic shared objects that are linked into a process.
The gdb(1) infoshared command also shows the shared libraries being used by a process, so that one can
obtain similar output to pldd using a command such as the following (to monitor the process with the
specified pid):
$ gdb-ex"setconfirmoff"-ex"setheight0"-ex"infoshared"\-ex"quit"-p$pid|grep'^0x.*0x'Options
--help-? Display a help message and exit.
--usage
Display a short usage message and exit.
--version-V Display program version information and exit.
See Also
ldd(1), lsof(1), dlopen(3), ld.so(8) Linux man-pages 6.9.1 2024-06-15 pldd(1)
Standards
None.
Synopsis
plddpidplddoption
Versions
Some other systems have a similar command.
