Man Page er_archive.1
NAME
er_archive - construct function and module lists for a
Forte(TM) Developer performance experiment
SYNOPSIS
er_archive [ -q ] [ -F ] experiment
er_archive -V
DESCRIPTION
er_archive is intended to be automatically run when an
experiment completes normally, or upon initial invocation of
the analyzer or er_print command on an experiment. It reads
the list of shared objects referenced in the experiment, and
constructs an archive file for each. Each output file is
named with a suffix of .archive, and contains function and
module mappings for the shared object.
If the target program terminates abnormally, er_archive
might not be run. If the user wishes to examine the experi-
ment on a different machine from the one on which it was
recorded, er_archive must be manually run on the experiment,
on the machine on which the data was recorded.
A .archive file is generated for all shared objects referred
to in the experiment. If the shared object can not be
found, or if it has a timestamp differing from that recorded
in the experiment, or if er_archive is run on a different
machine from that on which the experiment was recorded, the
.archive contains a warning. Warnings are also written to
stderr whenever er_archive is run manually (without the -q
flag).
OPTIONS
-q Do not write any warnings to stderr. Warnings are
incorporated into the .archive file, and shown in
the analyzer or er_print output.
-F Force writing or rewriting of .archive files.
This argument can be used to run er_archive by
hand, to rewrite files that had warnings.
-V Write version number information for er_archive
and exit.
COMPATIBILITY
er_archive does not work on experiments recorded with ear-
lier versions of the tools. If invoked on such experiments,
a warning is printed. Use the version of er_archive from
the release with which the experiment was recorded.
SEE ALSO
collect(1), collector(1), er_print(1), and the manual
Program Performance Analysis Tools