2
Management
43
Crashdump file naming
Every
crashdump
file
has
a
file
type
of
.dump
.
The
complete
filename
follows
the
format:
<date><time><module>.dump
Where
<module>
identifies
the
SEG
module
that
is
the
source
of
the
crashdump,
preceded
by
the
date
and
time
of
when
the
crash
occurred.
For
example:
2011
‐
01
‐
01_00.00.36_rtbld.dump
Note:
The
date
and
times
used
in
crashdump
timestamps
are
based
on
GMT.
They
are
not
based
on
local
time.
Displaying file contents
Crashdump
files
can
contain
a
readable
text
portion,
combined
with
any
binary
dump
information.
The
‐
cat
option
prints
out
only
the
readable
portion
of
a
crashdump
file.
For
example,
to
list
the
readable
contents
of
the
file
2011
‐
01
‐
01_00.00.52_dpcore.dump
,
use
the
CLI
command:
Device:/>
crashdump
‐
cat=2011
‐
01
‐
01_00.00.52_dpcore.dump
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Date:
2011
‐
01
‐
01
00:00:52
Version:
1.0.0.3
‐
1095
TP
Uptime:
50s
Dump
Record:
022
Event:
Exception
Reason:
Unhandled
exception=>TLB
exception
(load/instruction
fetch)
CPU
(core
‐
0)
state:
r0
($00):
0x0000000000000000
s0
($16):
0x00000000163ffe70
at
($01):
0x0000000000ffff80
s1
($17):
0xffffffff800cfaa0
v0
($02):
0x0000000000000000
s2
($18):
0xffffffff8004af40
v1
($03):
0x000000001018f83c
s3
($19):
0xffffffffffffffff
a0
($04):
0x00000000102e22f8
s4
($20):
0xffffffff800d0a30
"
"
"
If
the
same
command
is
applied
to
another
type
of
crashdump
file,
the
output
might
be
shorter
and
similar
to
the
example
below:
Device:/>
crashdump
‐
cat=2011
‐
01
‐
01_00.00.36_rtbld.dump
Date:
2011
‐
01
‐
01
00:00:36
Version:
1.0.0.3
‐
1095
TP
Application:
rtbld
PID:
734
Signal:
11
