Lines Matching full:line
19 'perf probe' [options] --line='LINE'
26 without debuginfo, or by C expressions (C line numbers, C function names,
63 --line=::
65 which specifies a range of the source code. (see LINE SYNTAX for detail)
106 2) Define event based on source file with line number
114 'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is the offset from function entry address in bytes, ':RLN' is the relative-line number from function entry line, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In addition, '@SRC' specifies a source file which has that function.
115 It is also possible to specify a probe point by the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, ':ALN' is the line number and ';PTN' is the lazy matching pattern.
127 LINE SYNTAX
129 Line range is described by following syntax.
133 FUNC specifies the function name of showing lines. 'RLN' is the start line
134 number from function entry line, and 'RLN2' is the end line number. As same as
135 probe syntax, 'SRC' means the source file path, 'ALN' is start line number,
136 and 'ALN2' is end line number in the file. It is also possible to specify how
139 So, "source.c:100-120" shows lines between 100th to l20th in source.c file. And "func:10+20" shows 20 lines from 10th line of func function.
143 The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and target. So this accepts wildcards('*', '?') and character classes(e.g. [a-z], [!A-Z]).
148 This provides some sort of flexibility and robustness to probe point definitions against minor code changes. For example, actual 10th line of schedule() can be moved easily by modifying schedule(), but the same line matching 'rq=cpu_rq*' may still exist in the function.)
163 ./perf probe --line schedule
165 Add a probe on schedule() function 12th line with recording cpu local variable:
