You can specify Quantify options:
In the environment variables QUANTIFYOPTIONS or PUREOPTIONS
On the link line
Any options specified in environment variables take precedence over options specified on the link line.
Quantify can also collect performance data for Java applications running on a Solaris SPARC 32-bit Java virtual machine (JVM). For information about using Quantify options with Java code, click
Quantify options must begin with a hyphen; for example: -record-system-calls=no
Quantify ignores case, hyphens, and underscores in the option name. For example, the option -record-system-calls is equivalent to -record_system_calls and -RecordSystemCalls
Do not use a space on either side of the equal sign (=).
For options that take a list of directories, use colons (:) to separate directory names. For example: -forbidden-directories=/usr/home/program:/usr/home/program1
For options that take a list of signals, use commas (,) to separate signal names. For example: -handle-signals=SIGUSR1,SIGUSR2,SIGILL
You can use wildcards. For example, in filenames: program* matches program4, /dira/dirb/program.o, and /dira/dirb/program1.o.
You can use conversion characters when you specify filenames for options such as -filename-prefix, -log-file, -run-at-save, and -run-at-exit.
Quantify supports three types of options: boolean, string, and integer.
Boolean
options take the values yes or no, or true or false.
If you do not specify an explicit value, the value is yes. For example, the option settings -record-data
and -record-data=yes are identical.
String options can be a string of any kind. String options are used for programs, directories, file names, lists of file descriptor numbers, system call and signal numbers, shell commands, floating point numbers, and directory paths. If you do not specify an explicit value for a string option, the value is cleared. For example, the option -write-summary-file=./quantifyout routes Quantify reports to the file quantifyout in the current directory. The option -write-summary-file=, without a value, clears any default specification of a summary file and writes the reports to the standard output.
Integer options can be set to any whole number. For example, the option -max-threads=60 instructs Quantify to expect a maximum of 60 threads to be created during a run. Integer values cannot be cleared.
You can specify any Quantify option in the QUANTIFYOPTIONS and PUREOPTIONS environment variables. Values in PUREOPTIONS apply to Quantify, PureCoverage, and Purify software products. The values specified in QUANTIFYOPTIONS take precedence over PUREOPTIONS.
Quantify applies build-time options specified in environment variables when a Quantify'd application is built. Any build-time options on the link line override environment variables.
Quantify applies run-time options specified in environment variables when you run the Quantify'd program. The environment values in force when you run the program override any defaults specified on the link line.
If an option is specified more than once in an environment variable, Quantify applies the first value it sees. To add an overriding value for the -log-file option without changing other options specified, use a command like:
|
csh |
% setenv QUANTIFYOPTIONS "-log-file=new \ |
|
sh, ksh |
$ QUANTIFYOPTIONS="-log-file=new \ |
You can use the PUREOPTIONS environment variable to set options that apply to Quantify, PureCoverage, and Purify software products.
For example, if your site has a central shared file that is sourced by all users' .cshrc or .profile files, you can set -cache-dir=alternate/dir in the PUREOPTIONS environment variable to apply to all users.
You can specify any Quantify option on the link line. For example:
quantify -cache-dir=$HOME/qcache -always-use-cache-dir $CC ...
Quantify applies build-time options to the Quantify build command being run.
Quantify builds run-time options into the executable so that they become the default values for the Quantify'd executable. This is a convenient way to build a program with nonstandard default values for run-time options. For example, the link line:
% quantify -collection-granularity=function \
-record-system-calls=no cc ...
instructs Quantify to instrument the program at build time to collect data only at the function level, and at run time to avoid collecting system call data.
Note:
To make sure that run-time options you specify remain in effect whenever the executable is run, use the -ignore-run-time-environment option at build time.