MONCONTROL(3) BSD Programmer's Manual MONCONTROL(3) NNAAMMEE mmoonnccoonnttrrooll, mmoonnssttaarrttuupp - control execution profile SSYYNNOOPPSSIISS mmoonnccoonnttrrooll(_i_n_t _m_o_d_e); mmoonnssttaarrttuupp(_u___l_o_n_g _*_l_o_w_p_c, _u___l_o_n_g _*_h_i_g_h_p_c); DDEESSCCRRIIPPTTIIOONN An executable program compiled using the --ppgg option to cc(1) automatical- ly includes calls to collect statistics for the gprof(1) call-graph exe- cution 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 _g_m_o_n_._o_u_t, then gprof(1) can be used to examine the results. mmoonnccoonnttrrooll() selectively controls profiling within a program. When the program starts, profiling begins. To stop the collection of histogram ticks and call counts use mmoonnccoonnttrrooll(_0); to resume the collection of his- togram ticks and call counts use mmoonnccoonnttrrooll(_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 mmoonnccoonnttrrooll(). Programs that are not loaded with --ppgg may selectively collect profiling statistics by calling mmoonnssttaarrttuupp() with the range of addresses to be pro- filed. _l_o_w_p_c and _h_i_g_h_p_c specify the address range that is to be sampled; the lowest address sampled is that of _l_o_w_p_c and the highest is just below _h_i_g_h_p_c. Only functions in that range that have been compiled with the --ppgg option to cc(1) will appear in the call graph part of the output; howev- er, all functions in that address range will have their execution time measured. Profiling begins on return from mmoonnssttaarrttuupp(). FFIILLEESS gmon.out execution data file SSEEEE AALLSSOO cc(1), gprof(1), profil(2) 4th Berkeley Distribution June 4, 1993 1