Lines Matching +full:line +full:- +full:name
9 debug-print code to obtain additional kernel information.
22 - source filename
23 - function name
24 - line number (including ranges of line numbers)
25 - module name
26 - format string
27 - class name (as known/declared by each module)
34 :#> head -n7 /proc/dynamic_debug/control
43 The 3rd space-delimited column shows the current flags, preceded by
55 :#> ddcmd '-p; module main func run* +p'
70 also under the mount-dir, typically ``/sys/kernel/debug/``.
78 :#> ddcmd file svcsock.c line 1603 +p
79 :#> ddcmd "file svcsock.c line 1603 +p"
80 :#> ddcmd ' file svcsock.c line 1603 +p '
90 :#> cat query-batch-file > /proc/dynamic_debug/control
101 command ::= match-spec* flags-spec
103 The match-spec's select *prdbgs* from the catalog, upon which to apply
104 the flags-spec, all constraints are ANDed together. An absent keyword
112 match-spec ::= 'func' string |
117 'line' line-range
119 line-range ::= lineno |
120 '-'lineno |
121 lineno'-' |
122 lineno'-'lineno
124 lineno ::= unsigned-int
128 ``line-range`` cannot contain space, e.g.
129 "1-30" is valid range but "1 - 30" is not.
135 The given string is compared against the function name
142 The given string is compared against either the src-root relative
150 file inode.c:1-100 # parse :tail as a line-range (above)
153 The given string is compared against the module name
154 of each callsite. The module name is the string as
156 suffix and with ``-`` changed to ``_``. Examples::
185 class JUNK # silent non-match
188 line
189 The given line number or range of line numbers is compared
190 against the line number of each ``pr_debug()`` callsite. A single
191 line number matches the callsite line number exactly. A
192 range of line numbers matches any callsite between the first
193 and last line number inclusive. An empty first number means
194 the first line in the file, an empty last line number means the
195 last line number in the file. Examples::
197 line 1603 // exactly line 1603
198 line 1600-1605 // the six lines from line 1600 to line 1605
199 line -1605 // the 1605 lines from line 1 to line 1605
200 line 1600- // all lines from line 1600 to the end of the file
206 - remove the given flags
215 Decorator flags add to the message-prefix, in order:
217 m Include module name
218 f Include the function name
219 l Include line number
224 Note the regexp ``^[-+=][flmpt_]+$`` matches a flags specification.
225 To clear all flags at once, use ``=_`` or ``-flmpt``.
231 To activate debug messages for core code and built-in modules during
251 If ``foo`` module is not built-in, ``foo.dyndbg`` will still be processed at
283 ``foo`` is extracted from the param-name, and applied to each query in
284 ``QUERY``, and only 1 match-spec of each type is allowed.
288 - modules do not need to define it explicitly
289 - every module gets it tacitly, whether they use pr_debug or not
290 - it doesn't appear in ``/sys/module/$module/parameters/``
293 For ``CONFIG_DYNAMIC_DEBUG`` kernels, any settings given at boot-time (or
294 enabled by ``-DDEBUG`` flag during compilation) can be disabled later via
297 echo "module module_name -p" > /proc/dynamic_debug/control
304 // enable the message at line 1603 of file svcsock.c
305 :#> ddcmd 'file svcsock.c line 1603 +p'
317 :#> ddcmd 'func svc_process -p'
331 // boot-args example, with newlines and comments for readability
332 Kernel command line: ...
353 debug and add ``ccflags := -DDYNAMIC_DEBUG_MODULE`` into the Makefile of any
368 Otherwise, they are off by default; ``ccflags += -DDEBUG`` or