Coverity使用"cov-build"为构建定义了哪些预处理器符号？

Question

我们将Coverity的Scan Build服务用于免费和开源项目.我正在研究两个关于受污染参数的Coverity发现(TAINTED_SCALAR).污点是误报,所以我试图用Coverity来检测代码__coverity_tainted_data_sanitize__以清除问题.

我想保护需要使用的代码,__coverity_tainted_data_sanitize__因为该函数仅用于使用Coverity cov-build工具的分析构建.也就是说,我想做的事情如下:

void Foo(std::istream& is, ...)
{
    std::string name;
    is >> name;

#if <SOME_COVERITY_PREPROCESSOR_MACRO>
    __coverity_tainted_data_sanitize__(name);
#endif

    ...
}

Coverity有几个使用示例__coverity_tainted_data_sanitize__,但他们没有展示如何保护它.例如,参见Tainted Scalar的函数模型示例和Explicitly文档参数传递机制.在询问预处理器时我也找不到它(见下文).

Coverity定义了哪些预处理器宏来确定分析构建？

---

预处理器输出

$ cov-build --dir ~/temp cpp -x c++ -dM </dev/null 2>&1 | egrep -i "(cov|anal)"
Coverity Build Capture (64-bit) version 7.7.0.4 on Linux 3.13.0-68-generic x86_64

---

环境变量

我确实找到了一些环境变量,但我更愿意避免将环境变量映射到预处理器定义.

$ cov-build --dir ~/temp printenv 2>&1 | egrep -i "(cov|anal)"
Coverity Build Capture (64-bit) version 7.7.0.4 on Linux 3.13.0-68-generic x86_64
LD_LIBRARY_PATH=/home/cov-analysis/jars
LD_PRELOAD=/home/cov-analysis/bin/libcapture-linux64-${PLATFORM}.so
COVERITY_TEMP=/tmp/cov-98db841699284e11e33be37fe7061776
COVERITY_LD_LIBRARY_PATH=/home/cov-analysis/jars
COVERITY_JAVA14_WARNING_FILE=/home/temp/warn_about_java14_compilations
COVERITY_ENABLE_CEJ_PER_CLASS_ERROR_RECOVERY=1
COVERITY_IS_COMPILER_DESCENDANT=0
COVERITY_CONFIG_FILE=/home/cov-analysis/config/coverity_config.xml
COVERITY_COMMON_TEMP=/tmp
COVERITY_JAVA_CONFIG=javac#TEMPLATE##java#TEMPLATE##apt#TEMPLATE##javaw#TEMPLATE###
COVERITY_PREV_XML_CATALOG_FILES=
COVERITY_OUTPUT_ENCODING=UTF-8
COVERITY_COMPILER_PATH_MISMATCH_FILE=/home/temp/has_path_mismatches
COVERITY_ENABLE_CECS_WATCHDOG=1
COVERITY_PATHLESS_CONFIGS_FILE=/home/temp/has_pathless_configs
COVERITY_LD_PRELOAD=/home/cov-analysis/bin/libcapture-linux64-${PLATFORM}.so
COVERITY_BUILD_INVOCATION_ID=1
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/cov-analysis/bin
COVERITY_BIN=/home/cov-analysis/bin
COVERITY_IDIR=/home/temp
COVERITY_TOP_PROCESS=0
COVERITY_OUTPUT=/home/temp/build-log.txt
COVERITY_EMIT=/home/temp/emit
PWD=/home/cov-analysis
COVERITY_SITE_CC=VBCSCompiler;apt;c++;cc;cl;clang;clang++;csc;csc2;devenv;g++;g++-4.8;g++-4.9;g++-5.1.0;gcc;gcc-4.8;gcc-4.9;gcc-5.1.0;java;javac;javaw;ld;msbuild;xgcc
COVERITY_LOG=/home/temp/build-log.txt
COVERITY_SYSTEM_ENCODING=UTF-8
COVERITY_TOP_CONFIG=/tmp/cov-98db841699284e11e33be37fe7061776/cov-configure/coverity_config.xml
COVERITY_IS_COMPILER=0

---

为了防止它被讨论......图书馆确实阅读了看似有污点的价值.但是,它是一个用于自我测试的数据文件,它位于其中/usr/share,而不是任意用户输入.该库不会向用户公开此特定功能,因此我不相信它会以意想不到的方式被滥用.

Answer 1

cov-emit和cov-internal-emit-clang都预定义了__COVERITY__宏,这可能是你想要的.

也就是说,我认为您应该能够在Coverity Scan Web UI中将缺陷标记为误报,并且它将不再显示.

$ cov-build --dir~/temp cpp -x c ++ -dM&1 | egrep -i"(cov | anal)"Linux 3.13.0-68-通用x86_64上的Coverity Build Capture(64位)版本7.7.0.4

顺便说一下,这是查看预定义的宏cpp,而不是cov-translate.据我所知,目前没有直接的方法来转储由cov-build/cov-translate预定义的所有宏.