trace-cmd-check-events - Man Page

parse the event formats on local system

Synopsis

trace-cmd check-events [Options]

Description

The trace-cmd(1) check-events parses format strings for all the events on the local system. It returns whether all the format strings can be parsed correctly. It will load plugins unless specified otherwise.

This is useful to check for any trace event format strings which may contain some internal kernel function references which cannot be decoded outside of the kernel. This may mean that either the unparsed format strings of the trace events need to be changed or that a plugin needs to be created to parse them.

Options

-N
- Don’t load plugins
--verbose[=level]

Set the log level. Supported log levels are "none", "critical", "error", "warning", "info", "debug", "all" or their identifiers "0", "1", "2", "3", "4", "5", "6". Setting the log level to specific value enables all logs from that and all previous levels. The level will default to "info" if one is not specified.

Example: enable all critical, error and warning logs
trace-cmd check-events --verbose=warning

See Also

trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1), trace-cmd-start(1)

Author

Written by Vaibhav Nagarnaik, <vnagarnaik@google.com[1]>

Resources

https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/

Copying

Copyright (C) 2011 Google, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

Notes

1.

vnagarnaik@google.com
mailto:vnagarnaik@google.com

Referenced By

trace-cmd(1).

07/23/2022 libtracefs Manual