1TRACE-CMD-CHECK_EV(1) libtracefs Manual TRACE-CMD-CHECK_EV(1)
2
3
4
6 trace-cmd-check-events - parse the event formats on local system
7
9 trace-cmd check-events [OPTIONS]
10
12 The trace-cmd(1) check-events parses format strings for all the events
13 on the local system. It returns whether all the format strings can be
14 parsed correctly. It will load plugins unless specified otherwise.
15
16 This is useful to check for any trace event format strings which may
17 contain some internal kernel function references which cannot be
18 decoded outside of the kernel. This may mean that either the unparsed
19 format strings of the trace events need to be changed or that a plugin
20 needs to be created to parse them.
21
23 -N - Don’t load plugins
24
25 --verbose[=level]
26 Set the log level. Supported log levels are "none", "critical",
27 "error", "warning", "info", "debug", "all" or their identifiers
28 "0", "1", "2", "3", "4", "5", "6". Setting the log level to
29 specific value enables all logs from that and all previous levels.
30 The level will default to "info" if one is not specified.
31
32 Example: enable all critical, error and warning logs
33
34 trace-cmd check-events --verbose=warning
35
37 trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
38 trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
39 trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1),
40 trace-cmd-start(1)
41
43 Written by Vaibhav Nagarnaik, <vnagarnaik@google.com[1]>
44
46 https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/
47
49 Copyright (C) 2011 Google, Inc. Free use of this software is granted
50 under the terms of the GNU Public License (GPL).
51
53 1. vnagarnaik@google.com
54 mailto:vnagarnaik@google.com
55
56
57
58libtracefs 04/15/2022 TRACE-CMD-CHECK_EV(1)