Home | History | Annotate | Download | only in info

Lines Matching full:lines

176 lines.  *Note Line-by-line::.
385 The `-t' option causes the NUM most active source lines in each
451 Sets width of output lines to WIDTH. Currently only used when
455 `--all-lines'
457 only the lines at the beginning of a basic-block are annotated.
516 histogram hits to be charged to individual source code lines,
705 * Line-by-line:: `gprof' can analyze individual source code lines
856 The lines full of dashes divide this table into "entries", one for
857 each function. Each entry has one or more lines.
861 the entry is for. The preceding lines in the entry describe the
862 callers of this function and the following lines describe its
874 * Callers:: Details of caller-lines' contents.
875 * Subroutines:: Details of subroutine-lines' contents.
954 5.2.2 Lines for a Function's Callers
958 These lines' fields correspond to the fields of the primary line, but
961 For reference, we repeat two lines from the entry for the function
995 has no entry of its own, it still has caller-lines in the entries
1008 5.2.3 Lines for a Function's Subroutines
1012 words, a line for each other function that it called. These lines'
1016 For reference, we repeat two lines from the entry for the function
1150 the subroutine lines for these functions.
1153 lines count only subroutines outside the cycle. Even though `a' calls
1178 These lines show how many times each function in the cycle called or
1180 `children' fields in these lines are blank because of the difficulty of
1191 functions, but to individual lines of source code. The program usually
1193 generate debugging symbols for tracking source code lines.
1198 lines to the enclosing function. The call graph does, however, show
1228 four histogram hits are broken down into four lines of source code -
1229 one hit occurred on each of lines 349, 351, 382 and 385. In the call
1422 subroutine lines.
1462 How do I find which lines in my program were executed the most times?
1468 This listing will show you the lines in your code executed most
1471 How do I find which lines in my program called a particular function?
1510 of recursive calls. GNU `gprof' omits these lines and puts the
1835 and can cause each of two adjacent lines to be credited with half a