Using the chroot Command with Shared Libraries
Some users may use the chroot
Conversely, if you move a program that uses shared libraries into a chrooted environment, you must have a copy of the dynamic loader, dld.so, and all required shared libraries in the correct locations.
Profiling Limitations
Profiling with the prof(1) and gprof(1) commands and the monitor library function is only possible on a contiguous chunk of the main program (a.out). Since shared libraries are not contiguous with the main program in virtual memory, they cannot be profiled. You can still profile the main program, though. If profiling of libraries is required, relink the application with the archive version of the library, using the
Summary of
What libraries your system has depends on what components were purchased. For example, if you did not purchase Starbase Display List, you cannot have the Starbase Display List library on your system.
Each library routine, or group of library routines, is documented on a man page. Man pages are sorted alphabetically by routine name and have the general form routine(nL), where:
routine | is the name of the routine, or group of closely related routines, being documented. |
nis the
L | is a letter designating the library in which the routine is stored. |
For example, the printf(3S) manpage describes the standard input/output libc routines printf, nl_printf, fprintf, nl_fprintf, sprintf, and nl_sprintf. And the pipe(2) manpage describes the pipe system call.
The major library groups defined in the
NOTE: Certain
Group | Description |
(2)These functions are known as system calls. They provide
(3C) These are standard C library routines located in libc.
Summary of