DataMuseum.dk

top - metrics - download

    Length: 1337 (0x539)
    Types: TextFile
    Notes: UNIX file
    Names: »profil.2«

└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
    └─⟦28c352965⟧ »/a« UNIX Filesystem
        └─⟦this⟧ »usr/man/man2/profil.2« 

TextFile

.ig
	@(#)profil.2	2.1	7/1/84
	@(#)Copyright (C) 1983 by National Semiconductor Corp.
..
.TH PROFIL 2 
.SH NAME
profil \- execution time profile
.SH SYNOPSIS
.nf
.B profil(buff, bufsiz, offset, scale)
.B char *buff;
.B int bufsiz, offset, scale;
.fi
.SH DESCRIPTION
.I Buff
points to an area of core whose length (in bytes) is given by
.IR bufsiz .
After this call, the user's program counter (pc)
is examined each clock tick (60th second);
.I offset
is subtracted from it, and the result multiplied by
.IR scale .
If the resulting number corresponds to a word
inside
.I buff,
that word is incremented.
.PP
The scale is interpreted as an unsigned,
fixed-point fraction with binary point at the
left: 01777778 gives a 1-1 mapping of pc's to words
in
.I buff;
0777778 maps each pair of instruction words
together.
028 maps all instructions onto the beginning of
.I buff
(producing a non-interrupting core clock).
.PP
Profiling is turned off by giving a
.I scale
of 0 or 1.
It is rendered
ineffective by giving a
.I bufsiz
of 0.
Profiling is turned off when an
.I exec
is executed, but remains on in child and parent both
after a
.IR fork .
.SH "SEE ALSO"
monitor(3), prof(1)
.SH BUGS
Profiling does not work for interpreters; if a signal were given
to a process when its cpu-time clock ticked then profiling interpreters
would be possible.