clang-tools 22.0.0git
clang::tidy::bugprone::CommandProcessorCheck Class Reference

Execution of a command processor can lead to security vulnerabilities, and is generally not required. More...

#include <CommandProcessorCheck.h>

Inheritance diagram for clang::tidy::bugprone::CommandProcessorCheck:
[legend]

Public Member Functions

 CommandProcessorCheck (StringRef Name, ClangTidyContext *Context)
void registerMatchers (ast_matchers::MatchFinder *Finder) override
void check (const ast_matchers::MatchFinder::MatchResult &Result) override

Detailed Description

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: https://clang.llvm.org/extra/clang-tidy/checks/bugprone/command-processor.html

Definition at line 23 of file CommandProcessorCheck.h.

Constructor & Destructor Documentation

◆ CommandProcessorCheck()

clang::tidy::bugprone::CommandProcessorCheck::CommandProcessorCheck ( StringRef Name,
ClangTidyContext * Context )
inline

Definition at line 25 of file CommandProcessorCheck.h.

Member Function Documentation

◆ check()

void clang::tidy::bugprone::CommandProcessorCheck::check ( const ast_matchers::MatchFinder::MatchResult & Result)
override

Definition at line 31 of file CommandProcessorCheck.cpp.

◆ registerMatchers()

void clang::tidy::bugprone::CommandProcessorCheck::registerMatchers ( ast_matchers::MatchFinder * Finder)
override

Definition at line 16 of file CommandProcessorCheck.cpp.


The documentation for this class was generated from the following files: