72 lines
1.4 KiB
HTML
72 lines
1.4 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>postmort(1)</TITLE>
|
|
</HEAD>
|
|
<BODY>
|
|
<H1>postmort(1)</H1>
|
|
<HR>
|
|
<PRE>
|
|
|
|
</PRE>
|
|
<H2>NAME</H2><PRE>
|
|
postmort - perform post-mortem on PC Minix core files
|
|
|
|
|
|
</PRE>
|
|
<H2>SYNOPSIS</H2><PRE>
|
|
<STRONG>postmort</STRONG> [<STRONG>-dpt</STRONG>] <STRONG>-c</STRONG> <EM>corefile</EM> <STRONG>-s</STRONG> <EM>symbfile</EM>
|
|
|
|
|
|
</PRE>
|
|
<H2>OPTIONS</H2><PRE>
|
|
|
|
<STRONG>-c</STRONG> Use the named corefile
|
|
|
|
<STRONG>-d</STRONG> Dump all text symbols and segment data
|
|
|
|
<STRONG>-p</STRONG> Display the kernel process table
|
|
|
|
<STRONG>-s</STRONG> Use the named symbol file
|
|
|
|
<STRONG>-t</STRONG> Display a stack backtrace
|
|
|
|
|
|
</PRE>
|
|
<H2>EXAMPLES</H2><PRE>
|
|
|
|
<STRONG>postmort</STRONG> # display the data from the file 'core'
|
|
|
|
|
|
</PRE>
|
|
<H2>DESCRIPTION</H2><PRE>
|
|
|
|
<EM>Postmort</EM> does a simple static analysis of a PC Minix core file; By
|
|
default, it looks for the file 'core' in the local directory and loads
|
|
that for analysis; it also searches for the file 'symbol.out', and if
|
|
that fails 'a.out', expecting them to contain symbol information for the
|
|
core file. It is not a fatal error if the symbol files don't exist.
|
|
|
|
The stack backtrace is slightly tricky, and may go on longer than is
|
|
really justified, since there's no easy way for it to know when to stop.
|
|
Treat its results with caution.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
</BODY>
|
|
</HTML>
|