1.\" Copyright (c) 1980, 1991, 1992, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)moncontrol.3 8.1 (Berkeley) 6/4/93 33.\" 34.Dd June 4, 1993 35.Dt MONCONTROL 3 36.Os BSD 4 37.Sh NAME 38.Nm moncontrol , 39.Nm monstartup 40.Nd control execution profile 41.Sh SYNOPSIS 42.Fn moncontrol "int mode" 43.Fn monstartup "u_long *lowpc" "u_long *highpc" 44.Sh DESCRIPTION 45An executable program compiled using the 46.Fl pg 47option to 48.Xr cc 1 49automatically includes calls to collect statistics for the 50.Xr gprof 1 51call-graph execution profiler. 52In typical operation, profiling begins at program startup 53and ends when the program calls exit. 54When the program exits, the profiling data are written to the file 55.Em gmon.out , 56then 57.Xr gprof 1 58can be used to examine the results. 59.Pp 60.Fn moncontrol 61selectively controls profiling within a program. 62When the program starts, profiling begins. 63To stop the collection of histogram ticks and call counts use 64.Fn moncontrol 0 ; 65to resume the collection of histogram ticks and call counts use 66.Fn moncontrol 1 . 67This feature allows the cost of particular operations to be measured. 68Note that an output file will be produced on program exit 69regardless of the state of 70.Fn moncontrol . 71.Pp 72Programs that are not loaded with 73.Fl pg 74may selectively collect profiling statistics by calling 75.Fn monstartup 76with the range of addresses to be profiled. 77.Fa lowpc 78and 79.Fa highpc 80specify the address range that is to be sampled; 81the lowest address sampled is that of 82.Fa lowpc 83and the highest is just below 84.Fa highpc . 85Only functions in that range that have been compiled with the 86.Fl pg 87option to 88.Xr cc 1 89will appear in the call graph part of the output; 90however, all functions in that address range will 91have their execution time measured. 92Profiling begins on return from 93.Fn monstartup . 94.Sh FILES 95.Bl -tag -width Pa -compact 96.It Pa gmon.out execution data file 97.El 98.Sh SEE ALSO 99.Xr cc 1 , 100.Xr gprof 1 , 101.Xr profil 2 102