Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pddump(1) [osf1 man page]

pddump(1)						      General Commands Manual							 pddump(1)

pddump - Dump profiling data files SYNOPSIS
pddump file... OPERANDS
A data file generated by a profiled program. A valid file is identified as a "profiling data file" by the file(1) command. DESCRIPTION
The pddump command displays, on the standard output, the record definitions and data of the specified profiling data files. Each file's dump is prefixed by the line "File = file:". This is followed by the file's field-alignment option and a list containing the file's name/value attribute pairs and the file's record definitions. Then each record in the file is dumped, showing the name of the record and the name and value of each of its fields. Strings are printed within double quotes, unsigned integers are printed in hexadecimal, and signed integers and floating-point numbers are printed in decimal. Non-array data lines contain equal signs to assist in filtering. The content of the profiling data files produced by Tru64 UNIX may be expanded in future releases, but Tru64 UNIX tools will continue to support older formats. To write tools that process Tru64 UNIX profiling data files, use the pdtostd(1) command to convert the Tru64 UNIX formats to industry standard formats, where a standard format exists. Alternatively, use the libpdf.a utilities to read the profiling data files directly, skipping any new attributes, records, or fields that may appear. FILES
Library of routines for reading and writing profiling data files Header file for libpdf.a SEE ALSO
Commands: atom(1), cc(1), file(1), kprofile(1), pdtostd(1), uprofile(1) AtomTools: hiprof(5), pixie(5) Programmer's Guide pddump(1)

Check Out this Related Man Page

MONCONTROL(3)						   BSD Library Functions Manual 					     MONCONTROL(3)

moncontrol, monstartup -- control execution profile LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
moncontrol(int mode); monstartup(u_long *lowpc, u_long *highpc); DESCRIPTION
An executable program compiled using the -pg option to cc(1) automatically includes calls to collect statistics for the gprof(1) call-graph execution profiler. In typical operation, profiling begins at program startup and ends when the program calls exit. When the program exits, the profiling data are written to the file gmon.out, then gprof(1) can be used to examine the results. moncontrol() selectively controls profiling within a program. When the program starts, profiling begins. To stop the collection of his- togram ticks and call counts use moncontrol(0); to resume the collection of histogram ticks and call counts use moncontrol(1). This feature allows the cost of particular operations to be measured. Note that an output file will be produced on program exit regardless of the state of moncontrol(). Programs that are not loaded with -pg may selectively collect profiling statistics by calling monstartup() with the range of addresses to be profiled. lowpc and highpc specify the address range that is to be sampled; the lowest address sampled is that of lowpc and the highest is just below highpc. Only functions in that range that have been compiled with the -pg option to cc(1) will appear in the call graph part of the output; however, all functions in that address range will have their execution time measured. Profiling begins on return from monstartup(). ENVIRONMENT
PROFDIR Directory to place the output file(s) in. When this is set, instead of writing the profiling output to gmon.out, a filename is gen- erated from the process id and name of the program (e.g., 123.a.out). If you are profiling a program that forks, or otherwise cre- ates multiple copies, setting this is the only reasonable way to get all profiling data. FILES
gmon.out execution data file SEE ALSO
cc(1), gprof(1), profil(2) BSD
June 4, 1993 BSD
Man Page