This soft copy for use by IBM employees only.
> stat (to show machine status at time of crash)
> status
CPU
The
information includes CPU number, thread ID, thread table slot, process ID,
process table slot and process name. In our example,
process slot 46. To see further information about this process:
> p -r
SLT ST
26 a
46 a
0452-1004: Cannot read process table entry 37.
(Ignore messages reading "cannot read process table entry.")
This shows that the process running at the time of the crash was
and it was running in slot 46. It also shows
the stack trace for
> t 26
STACK TRACE:
The
image, a core image, or the running kernel. It also interprets and formats
control structures in the system and certain miscellaneous functions for
examining a dump.
In order to analyze the dump, you must execute the
/unix, and it must be the /unix of the system that had the problem. However, to
make any change to code, you must have the source AIX code which is not held
by customers. Therefore, there is not much more that you can do. It is best to
let the Support Center handle the dump.
One useful operation you can do is to make sure that you have a good full dump.
If you see :
Reading in symbols
>
sysname: AIX
nodename: sp21n02
release: 1
version: 4
machine: 000168205700
time of crash: Tue Aug 6 15:38:38 1996
age of system: 7hr, 22min
abend code: 0
csa: 0x0
TID TSLOT
PID PSLOT PROC_NAME
0
2b43
43
2e3a
status
subcommand displays a description of the kernel process. The
PID
PPID
PGRP
2 a
204
0
FLAGS: swapped_in no_swap fixed_pri kproc
1aee
2da4
1aee
FLAGS: swapped_in
2e3a
2da4
2e3a
FLAGS: swapped_in
find
:
.et_wait()
.poll_wait()
.select()
.sys_call()
crash
command is an interactive utility for examining an operating system
46 sysdumpstart
UID EUID TCNT NAME
0
0
0
1 wait
0
0
1 find
0
0
1 sysdumpstart
find
was running in slot 26. To see
Chapter 8. Producing a System Dump
sysdumpstart
is in
sysdumpstart
crash
command against
211