CRASHINFO(8) BSD System Manager's Manual CRASHINFO(8)NAME
crashinfo -- analyze a core dump of the operating system
SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core]
DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as
the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX.
By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the
core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel
that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel
file can also be explicitly provided via the kernel argument.
Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8),
ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8).
The options are as follows:
-d crashdir
Specify an alternate core dump directory. The default crash dump directory is /var/crash.
-n dumpnr
Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory.
-k kernel
Specify an explicit kernel file.
SEE ALSO textdump(4), savecore(8)HISTORY
The crashinfo utility appeared in FreeBSD 6.4.
BSD June 28, 2008 BSD
Check Out this Related Man Page
crashutil(1M)crashutil(1M)NAME
crashutil - manipulate crash dump data
SYNOPSIS
version] source [destination]
DESCRIPTION
copies and preserves crash dump data, and performs format conversions on it. Common uses of include:
o Copying portions of a dump that still reside on a raw dump device into a crash dump directory.
o Converting between different formats of crash dumps.
o Copying crash dumps from one directory, or medium, to another.
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 if is not specified, 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 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.
There are three known dump formats:
(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 cor-
respondence 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.
(Version 1) This format, used in HP-UX 10.10, 10.20, and 10.30, consists of a directory containing an file, the kernel file, and numerous
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.
(Version 2) This format, used in HP-UX 11.00 and later, consists of a directory containing an file, the kernel and all dynamically loaded
kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing
which memory pages were dumped and which were not. sources or destinations of this type should be specified as the pathname
to a crash directory.
(Version 3) This format is used in HP-UX Release 11i Version 1.0 and later. It is very similar in structure to the format in that it
consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files,
each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which
were not. In addition to the primary file, there are auxiliary index files, that contain metadata describing the image files
containing the memory pages. This format will be used when the dump is compressed. See crashconf(1M).
Other formats, for example tape archival formats, may be added in the future.
When the source and destination are different types of files -- for example, when source is a directory and destination is a pair of plain
files -- both must be specified.
Options
(Quiet) Disables the printing of progress messages.
Warning and error messages are still printed.
Specifies the version of the destination format.
Allowed values are 0, 1, 2 or 3. Also allowed is the keyword which specifies that the destination format should be the same as
the current source format. is the default if is not specified. If the destination format is then the source format should
also be Conversion to from older formats is not supported.
RETURN VALUE
Upon exit, returns the following values:
0 The operation was successful.
1 The operation failed, and an appropriate error message was printed.
EXAMPLES
An HP-UX 11.00 crash dump was saved by savecrash(1M) to The flag was specified to savecrash, specifying that only those portions of the
dump which were endangered by swap activity should be saved; the rest are still resident in the raw dump devices. To save the remainder of
the dump into the crash dump directory, use:
If preferred, the completed crash dump directory could be in a different location -- perhaps on another machine via NFS:
To debug this crash dump using tools which do not understand the most current crash dump format, convert it to the older core directory
format:
or the even older "core file and kernel" format:
AUTHOR
was developed by HP.
SEE ALSO savecrash(1M), crashconf(1M).
crashutil(1M)