Man Pages

---

Back to Software Index  Manpage Top Level

Name

Synopsis

Availability

Description

Either both or neither of the -d and -n options must be specified. If neither is specified, trace output is extracted from the running kernel. If both are specified, the -d argument names the file containing the (crashed) system memory image, and the -n argument names the file containing the symbol table for the system memory image.

The TNF trace file tnf_file produced is exactly the same size as the in-core buffer; it is essentially a snapshot of that buffer. It is legal to run tnfxtract while kernel tracing is active, i.e., while the in-core buffer is being written. tnfxtract insures that the output file it generates is low-level consistent, i.e., that only whole probes are written out, and that internal data structures in the buffer are not corrupted because the buffer is being concurrently written.

The TNF trace file generated is suitable as input to tnfdump(1) , which will generate an ASCII file.

Options

-d dumpfile

Use dumpfile as the system memory image, instead of the running kernel. The dumpfile is normally the path name of a file generated by the savecore utility.

-n namelist

Use namelist as the file containing the symbol table information for the given dumpfile.

Operands

tnf_file

output file generated by tnfxtract based on kernel trace output from an in-core buffer in the Solaris kernel.

Examples

# Extract probes from the running kernel into ktrace.out.
example% tnfxtract ktrace.out

# Extract probes from a kernel crash dump into ktrace.out.
example% tnfxtract -d /var/crash/‘uname -n‘/vmcore.0 \
    -n /var/crash/‘uname -n‘/unix.0 ktrace.out

Exit Status

1. Successful completion.
   >0
   An error occurred.

   See Also

   prex(1) , tnfdump(1) , savecore(1M) , tnf_probes(4)

   ---

   Table of Contents

   • Name
   • Synopsis
   • Availability
   • Description
   • Options
   • Operands
   • Examples
   • Exit Status
   • See Also