Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   20652 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

er_archive(1)							 er_archive(1)

NAME
       er_archive  -  construct	 function  and	module lists for a performance
       experiment

SYNOPSIS
	      er_archive [ -nqFA ]  experiment.

	      er_archive -V

DESCRIPTION
       er_archive runs automatically 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 run.

       If the user wishes to examine the experiment  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 referenced  in  the
       experiment.  If the shared object cannot be found, or if it has a time‐
       stamp 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
       -n	 Archive  the  named  experiment  only, not any of its descen‐
		 dants.

       -q	 Do not write any warnings to stderr.  Warnings	 are  incorpo‐
		 rated	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.

       -A	 Request writing of all	 load  objects	to  experiment.	  This
		 argument  can	be  used to generate experiments that are more
		 readily copied to a machine other than the one on  which  the
		 experiment  was  recorded.   For  Java	 experiments, all .jar
		 files are also copied into the experiment.

       -V	 Write version number information for er_archive and exit.

COMPATIBILITY
       er_archive does not work on experiments recorded with earlier  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  experi‐
       ment was recorded.

SEE ALSO
       analyzer(1), collect(1), collector(1), er_print(1), and the
       Performance Analyzer manual.

				   May 2010			 er_archive(1)

Vote for polarhome