1TRACE-CMD-CHECK_EV(1) [FIXME: 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
26 trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
27 trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
28 trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1),
29 trace-cmd-start(1)
30
32 Written by Vaibhav Nagarnaik, <vnagarnaik@google.com[1]>
33
35 git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
36
38 Copyright (C) 2011 Google, Inc. Free use of this software is granted
39 under the terms of the GNU Public License (GPL).
40
42 1. vnagarnaik@google.com
43 mailto:vnagarnaik@google.com
44
45
46
47[FIXME: source] 03/23/2017 TRACE-CMD-CHECK_EV(1)