Compressed Dump

Compressed Dump White Paper, Version 1.3
page 19
crashutil(1M) crashutil(1M)
NAME
crashutil - manipulate crash dump data
SYNOPSIS
/usr/sbin/crashutil [-q] [-v version] source [destination]
DESCRIPTION
crashutil copies and preserves crash dump data, and performs format conversions
on it. Common uses of crashutil include:
+ Copying portions of a dump that still reside on a raw dump device into a crash
dump directory.
+ Converting between different formats of crash dumps.
+ Copying crash dumps from one directory, or medium, to another.
crashutil will write to its destination the crash dump it reads from its source. The
crash dump format used to write the destination is specified with -v; if -v is not spec-
ified, the destination will have the same format as the source. If no destination is
specified, source is used; the format conversion will be done in place in the source,
without copying. When crashutil completes successfully, the entire contents of the
crash dump will exist at destination; any portions that had still been on raw dump
devices will have been copied to destination.
The dump formats are:
COREFILE (Version 0) This format, used up through HP-UX 10.01,
consists of a single file containing the physical memory
image, with a 1-to-1 correspondence between file offset
and memory address. Normally there is an associated
file containing the kernel image. sources or destinations
of this type must be specified as two pathnames to plain
files, separated by whitespace; the first is the core image
file and the second is the kernel image file.
COREDIR (Version 1) This format, used in HP-UX 10.10, 10.20, and
10.30, consists of a core.n directory containing an INDEX
file, the kernel (vmunix) file, and numerous core.n.m files,
which contain portions of the physical memory image.
sources or destinations of this type should be specified
as the pathname to a core directory.
CRASHDIR (Version 2)This format, used in HP-UX 11.00 and later,
consists of a crash.n directory containing an INDEX file,
the kernel and all dynamically loaded kernel module files,
and numerous image.m.p files, each of which contain