Query: monitor
OS: v7
Section: 3
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
MONITOR(3) Library Functions Manual MONITOR(3)NAMEmonitor - prepare execution profileSYNOPSISmonitor(lowpc, highpc, buffer, bufsize, nfunc) int (*lowpc)( ), (*highpc)( ); short buffer[ ];DESCRIPTIONAn executable program created by `cc -p' automatically includes calls for monitor with default parameters; monitor needn't be called explicitly except to gain fine control over profiling. Monitor is an interface to profil(2). Lowpc and highpc are the addresses of two functions; buffer is the address of a (user supplied) array of bufsize short integers. Monitor arranges to record a histogram of periodically sampled values of the program counter, and of counts of calls of certain functions, in the buffer. The lowest address sampled is that of lowpc and the highest is just below highpc. At most nfunc call counts can be kept; only calls of functions compiled with the profiling option -p of cc(1) are recorded. For the results to be significant, especially where there are small, heavily used routines, it is suggested that the buffer be no more than a few times smaller than the range of locations sampled. To profile the entire program, it is sufficient to use extern etext(); ... monitor((int)2, etext, buf, bufsize, nfunc); Etext lies just above all the program text, see end(3). To stop execution monitoring and write the results on the file mon.out, use monitor(0); then prof(1) can be used to examine the results.FILESmon.outSEE ALSOprof(1), profil(2), cc(1) MONITOR(3)
Related Man Pages |
---|
monitor(3c) - opensolaris |
monstartup(3) - bsd |
moncontrol(3) - ultrix |
monstartup(3) - ultrix |
monstartup(3) - osx |
Similar Topics in the Unix Linux Community |
---|
<curses.h> |
Skipole Network Monitor 0.45 (Default branch) |
Skipole Network Monitor 0.50 (Default branch) |
Skipole Network Monitor 0.80 (Default branch) |
searching reverse in a file |