|
Option |
Default |
|
-chain-length |
6 |
|
Specifies the number of stack frames to be recorded and printed in the function call chain in a Purify message. This option also affects the extent of the red zone around memory blocks used by Purify to detect array-bound errors. Since Purify stores the call chain of the function allocating the memory in the red zone at the end of the block, you should set this to a larger value to increase the red zone and to increase the extent of the area where incorrect array boundary accesses can be detected. Larger values of chain-length also increase the amount of memory and swap space that your program uses. |
|
|
-show-directory |
no |
|
Shows the directory path for each file in the call chain if that information is available. This information might not be available if the file is not compiled with the compiler debugging option -g. The directory, if displayed, is stripped of the auto-mounter prefix. The format of the call chain looks similar to: func1[/home/myprogram/file.o] On HPUX, the -g option does not provide the full path to source files because the compiler does not provide that information.
|
|
|
-show-pc |
no |
|
Facilitates debugging by showing the full program counter (pc) value in each frame of the call chain. The format of the call chain is similar to: func1 [file.o pc=0x5678]
|
|
|
-show-pc-offset |
no |
|
Facilitates debugging by appending a pc-offset from the start of the function to each function name in the call chain. The format of the call chain looks similar to: func1 +0x1234 [file.o]
|
|
Related options include: