clang-tools
7.0.0
|
Execution of a command processor can lead to security vulnerabilities, and is generally not required. More...
#include <CommandProcessorCheck.h>
Public Member Functions | |
CommandProcessorCheck (StringRef Name, ClangTidyContext *Context) | |
void | registerMatchers (ast_matchers::MatchFinder *Finder) override |
Override this to register AST matchers with Finder . More... | |
void | check (const ast_matchers::MatchFinder::MatchResult &Result) override |
ClangTidyChecks that register ASTMatchers should do the actual work in here. More... | |
![]() | |
ClangTidyCheck (StringRef CheckName, ClangTidyContext *Context) | |
Initializes the check with CheckName and Context . More... | |
virtual void | registerPPCallbacks (CompilerInstance &Compiler) |
Override this to register PPCallbacks with Compiler . More... | |
DiagnosticBuilder | diag (SourceLocation Loc, StringRef Description, DiagnosticIDs::Level Level=DiagnosticIDs::Warning) |
Add a diagnostic with the check's name. More... | |
virtual void | storeOptions (ClangTidyOptions::OptionMap &Options) |
Should store all options supported by this check with their current values or default values for options that haven't been overridden. More... | |
Additional Inherited Members | |
![]() | |
StringRef | getCurrentMainFile () const |
Returns the main file name of the current translation unit. More... | |
LangOptions | getLangOpts () const |
Returns the language options from the context. More... | |
![]() | |
OptionsView | Options |
Execution of a command processor can lead to security vulnerabilities, and is generally not required.
Instead, prefer to launch executables directly via mechanisms that give you more control over what executable is actually launched.
For the user-facing documentation see: http://clang.llvm.org/extra/clang-tidy/checks/cert-env33-c.html
Definition at line 26 of file CommandProcessorCheck.h.
|
inline |
Definition at line 28 of file CommandProcessorCheck.h.
References registerMatchers().
|
overridevirtual |
ClangTidyChecks
that register ASTMatchers should do the actual work in here.
Reimplemented from clang::tidy::ClangTidyCheck.
Definition at line 36 of file CommandProcessorCheck.cpp.
|
overridevirtual |
Override this to register AST matchers with Finder
.
This should be used by clang-tidy checks that analyze code properties that dependent on AST knowledge.
You can register as many matchers as necessary with Finder
. Usually, "this" will be used as callback, but you can also specify other callback classes. Thereby, different matchers can trigger different callbacks.
If you need to merge information between the different matchers, you can store these as members of the derived class. However, note that all matches occur in the order of the AST traversal.
Reimplemented from clang::tidy::ClangTidyCheck.
Definition at line 20 of file CommandProcessorCheck.cpp.
Referenced by CommandProcessorCheck().