Solaris Application Programming, 1/e - Chapter 4 - Parent Directory

84 Chapter 4 Informational Tools
Example 4.49 Call Stack for malloc Requests Made by the Compiler (continued )
malloc
value ------------- Distribution ------------- count
0 | 0
1 | 2
2 |@@@ 21
4 |@@@@@@ 52
8 |@@@@@@@@@@@ 88
16 |@@@@@@@@ 65
32 |@@@@@@ 52
64 |@@@@@ 44
128 |@ 5
256 | 2
512 | 1
1024 | 0
4.5 Information about Applications
4.5.1 Reporting Library Linkage (ldd)
The ldd utility reports the shared libraries that are linked into an application.
This is useful for acquiring information, but it should not have any effect on performance
(unless the wrong version of a library is selected somehow).
The output in Example 4.50 shows the library the application is searching for on
the left, and the library that has been located on the right.
Example 4.50 Output from ldd Showing the Linking of a Particular Application
$ ldd ap27
libm.so.1 => /usr/lib/libm.so.1
libc.so.1 => /usr/lib/libc.so.1
/usr/platform/SUNW,Sun-Blade-2500/lib/libc_psr.so.1
Passing the -r option to ldd will cause it to check both the objects that are
linked into the application and the particular function calls that are required. It
will report whether the application is missing a library, and it will report the functions
that are missing.
The output shown in Example 4.51 is from the -r option passed to ldd. There
are two items of interest. First, ldd reports that it is unable to locate the libsunmath
library, which is Sun’s library of additional mathematical functions. Under
this option, ldd reports the two function calls that it is unable to locate, and these
function calls correspond to square root calls for single-precision floating-point,
and for long integers.