directory and $PATH. The executable path can be specified along with the pid/corepath, separated by a colon (:) character. Use the
The following exit values are returned: 0: Successful operation
Use the following options to view information for your specified files.
To | Use the option |
|
|
Print the usage menu | |
|
|
Print the start and end addresses of text and data segment mappings for the shared libraries | |
|
|
The
Example 4 Executing ‘pldd
27739: ./thread32 |
|
|
| |
Text start | Text end | Data start | Data end | Name |
0x04000000 | 0x04000f50 | 0x40010000 | 0x40010098 | ./thread32 |
0xc0018000 | 0xc00bb2d0 | 0x7efec000 | 0x7eff0a58 | /usr/lib/hpux32/dld.so |
0xc00bc000 | 0xc01c8970 | 0x7efe0000 | 0x7efe2e28 | /usr/lib/hpux32/libpthread.so.1 |
0xc01cc000 | 0xc04a4ce0 | 0x7efcc000 | 0x7efdfaa8 | /usr/lib/hpux32/libc.so.1 |
0xc04a8000 | 0xc04abf90 | 0x7efc4000 | 0x7efc4150 | /usr/lib/hpux32/libdl.so.1 |
|
|
|
|
|
Printing a Stack Trace with pstack(1)
Given the PID of a running process or the full path to a corefile, the pstack command prints the stack trace for each lwp thread in the process. To obtain symbol information, pstack searches load modules (executable/shared libraries) in the current directory, $PATH, $LD_LIBRARY_PATH, and $SHLIB_PATH. The executable path can be specified along with the
The pstack command works by attaching to the running process and reading its registers, memory, and stack. Mismatch between executable and corefile may result in unpredictable behavior.
The following exit values are returned: 0:Successful operation
Use the following options to view information for your specified files:
Table 8 Options to view information specified files
To view this | Use the option |
|
|
Print the usage menu | |
|
|
Print stack upto a specified level | |
| parameter) |
|
|
Print stack of only one thread using suspending execution of other threads | |
|
|
62 Linker Tools for