06-03-2005
You could use ldd.
ldd appl-name would show you the libraries that are used(needed) by app-name.
Vino
10 More Discussions You Might Find Interesting
1. HP-UX
HI,
I am dynamically loading shared libraries using shl_load(). There are multiple processes (50 or more) which loads the same shared library. Will Unix internally load only one copy of the shared library or it will load multiple copies.
Can I have memory issues if this is done.
Thanks,... (1 Reply)
Discussion started by: Debasisb2002
1 Replies
2. UNIX for Dummies Questions & Answers
Hello everyone. I am new to these forums and also new to Unix. And by saying "new to Unix" I mean I have never used it and 10 minutes ago was asked to start learning. So here I am.
I was wondering if anyone could help me find out how long it would take to write code in Unix that will do the... (1 Reply)
Discussion started by: idesaj
1 Replies
3. Programming
hi all,
i have a critical and specific problem with respect to set uid bit on user and the dll's
for a binary, (under the userid A)
it needs libraries from /usr/lib and informix libraries from $INFORMIXDIR/lib/esql
but this binary should be kicked off from id B,
hence s-bit on user is... (5 Replies)
Discussion started by: matrixmadhan
5 Replies
4. Programming
Hi everybody!
I would like to set in the makefile a path that should be the path where the program searches for the libraries loaded at run time.
Is there such a variable to be set in makefile?
Thanks in advance! (1 Reply)
Discussion started by: nadiamihu
1 Replies
5. Programming
anybody knows how to view loaded shared libraries by running processes in linux enviornment? any command or tool ?
thanks a lot (3 Replies)
Discussion started by: princelinux
3 Replies
6. UNIX for Advanced & Expert Users
I am trying to install a scientific program onto my mac and when i try and execute it this error comes up and i cant find any literature on the net to fix it...
dyld: Library not loaded: /usr/local/lib/libgfortran.2.dylib
Referenced from:... (4 Replies)
Discussion started by: olifu02
4 Replies
7. AIX
Hello guys, I have a trouble when running an application in AIX, I've compiled and the
LIBRARY_PATH seems ok, but I get the following message:
rtld: 0712-001 Symbol __pthread was referenced
from module main_app(), but a runtime definition
of the symbol was not found
ldd... (4 Replies)
Discussion started by: edgarvm
4 Replies
8. AIX
Hi,
I have a problem about loaded shared libraries. I'm issuing ‘procldd' for a process and AIX shows me the loaded shared libraries. I'm collecting these libraries and counting their size. They were 350MB. After this, I'm issuing ‘ps vx' and I'm seeing that the process takes 130MB from AIX's... (1 Reply)
Discussion started by: jhatzics
1 Replies
9. BSD
Heyas
Since freebsd has set TERM to xterm when in terminal mode, i'm very curious what its value will be in GUI mode - seems its xterm (in x11/twm) as well.. how smart :eek: :(
So i've installed: awesome and xorg, but when calling awesome, it talks something about invalid display.
So i've... (1 Reply)
Discussion started by: sea
1 Replies
10. UNIX for Advanced & Expert Users
hi,
would like to know if anyone knows or could verify and give me an answer on when autosys does actually load the profile whether in Activated state or Running state.
Scenerio am trying to look for is
Lets say i have a profile variable DATE=Mar052015
Start jobA --> JobB depends on A -->... (0 Replies)
Discussion started by: veshwar
0 Replies
LDD(1) Linux Programmer's Manual LDD(1)
NAME
ldd - print shared object dependencies
SYNOPSIS
ldd [option]... file...
DESCRIPTION
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
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)
In the usual case, ldd invokes the standard dynamic linker (see ld.so(8)) 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 ld.so(8)) and
load the objects that satisfy those dependencies. For each dependency, ldd displays the location of the matching object and the (hexadeci-
mal) address at which it is loaded. (The linux-vdso and ld-linux shared dependencies are special; see vdso(7) and ld.so(8).)
Security
Be aware that in some circumstances (e.g., where the program specifies an ELF interpreter other than ld-linux.so), 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. (In glibc versions before 2.27, the
upstream ldd implementation did this for example, although most distributions provided a modified version that did not.)
Thus, you should never employ ldd on an untrusted executable, since this may result in the execution of arbitrary code. A safer alterna-
tive 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
--version
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
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
pldd(1), sprof(1), ld.so(8), ldconfig(8)
COLOPHON
This page is part of release 4.15 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 https://www.kernel.org/doc/man-pages/.
2017-09-15 LDD(1)