libcrash.5 (2010 09)

l
libcrash(5) libcrash(5)
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 portions of the physical memory image
and metadata describing which memory pages were dumped and which were not.
PARDIR (Version 5) This format is used in
HP-UX Release 11i Version 1.0 and later. It is very simi-
lar in structure to the
CRASHDIR format in that it consists of a
crash.n directory con-
taining an
INDEX file, the kernel and all dynamically loaded kernel module files, and
numerous image.m.p files, each of which contain portions of the physical memory image
and metadata describing which memory pages were dumped and which were not. In addi-
tion to the primary INDEX 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 devices have compressed memory images. See crashconf (1M).
Other formats, for example tape archival formats, may be added in the future.
Cache
Caching mechanism is implemented to improve the performance while analyzing
PARDIR format crash
dumps. This caching mechanism is used to keep the uncompressed pages so that subsequent requests can
be satisfied from the cache. By default, this caching mechanism will be disabled. It can be enabled by
setting the environment variable
LIBCRASH_ENABLE_CACHE
. It will create the cached files in the
crash dump directory.
RETURN VALUE
Most of the calls in
libcrash return an integer status value. A zero return value indicates success. A
positive return value indicates some sort of warning, despite which the requested operation was com-
pleted. A negative return value indicates some sort of error, which prevented completion of the requested
operation. The values returned by the library are:
CR_OK Success.
CRWARN_NOEXPECTED
The expected size or checksum of one or more files in the crash dump
was not recorded, so the integrity of the dump cannot be verified. The
dump might be corrupt.
CRWARN_NOACTUAL The checksum of one or more files in the crash dump could not be com-
puted, so it could not be checked against the expected value. The dump
might be corrupt.
CRWARN_SWAPPEDON A raw device containing a portion of the crash dump has been swapped
on, so the dump is probably corrupt.
CRWARN_MISMATCH The size or checksum of one or more files in the crash dump did not
match what was expected. The dump is probably corrupt.
CRERR_NOPAGE A read or write request was issued for a memory address that does not
exist on the target machine.
CRERR_READONLY A write request was issued for a crash dump. Writes are supported only
to running systems through the /dev/mem driver.
CRERR_WRONGDUMP A raw dump device which is supposed to contain part of the dump does
not. It may have been overwritten by swap activity or by a more recent
dump.
CRERR_WRONGHOST A portion of the crash dump still resides on a dump device of the system
that dumped, which is not the current system.
CRERR_NONODE The specified node number does not exist.
CRERR_ERRNO A system error occurred. Consult errno for the specific error. Note
that certain values for errno have specific meanings in the context of
the library. They include:
[ENOEXEC] A portion of the crash dump could not be
uncompressed.
[ENOTDIR] The specified pathname for the dump was neither a
plain file, nor a directory containing an INDEX file, nor
the /dev/mem pseudodriver.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010