System Administration Guide
Appendix D, Using the crash(ADM) diagnostic tool

Determining the kernel component that failed

Determining the kernel component that failed

The information given by the panic and trap commands of the crash(ADM) command tells you which routines were executing just before the panic. Because the entire kernel (all kernel operating system code plus all driver code) is linked together into one executable file, this does not tell you which component caused the problem. Knowing which component contains the problematic function can sometimes tell you if the problematic function is part of the operating system, or if it is part of a driver supplied by another vendor.

This information can be extracted using the strings(C) command or, for systems where the SCO OpenServer Development System is installed, the nm(CP) command. Both methods are detailed below.

The following hints are provided for users who are not familiar with device driver conventions: