Installation guide

• dbx(1) - Describes the source level debugger.
13.6.2 Files Created and Used During Crash Dumps
By default, the savecore command copies crash dump file into
/var/adm/crash, although you can redirect crash dumps to any file
system that you designate. The following files are created or used during a
crash:
• /var/adm/crash/vmzcore.n – The crash dump file, named
vmcore.n if the file is non compressed (no z)
• /var/adm/crash/bounds – A text file that specifies the incremental
number of the next dump (The n in vmzcore.n)
• /var/adm/crash/minfree – The file that pecifies the minimum
number of kilobytes to be left after crash dump files are written
• /var/adm/crash/vmunix.n – A copy of the kernel that was running
at the time of the crash, typically of /vmunix.
• /etc/syslog.conf and /etc/binlog.conf – The logging
configuration files
13.6.3 Crash Dump Creation
After a system crash, you normally reboot your system by issuing the boot
command at the console prompt. During a system reboot, the
/sbin/savecore script invokes the savecore command. This command
moves crash dump information from the swap partitions into a file and
copies the kernel that was running at the time of the crash into another
file. You can analyze these files to help you determine the cause of a crash.
The savecore command also logs the crash in system log files.
You can invoke the savecore command from the command line. For
information about the command syntax, see the savecore
(8) reference
page.
13.6.3.1 Crash Dump File Creation
When the savecore command begins running during the reboot process, it
determines whether a crash dump occurred and whether the file system
contains enough space to save it. (The system saves no crash dump if you
shut it down and reboot it; that is, the system saves a crash dump only
when it crashes.)
If a crash dump exists and the file system contains enough space to save
the crash dump files, the savecore command moves the crash dump and a
Administering Events and Errors 13–17