当前位置：文江博客话题详情

禁用规则2.2检查器

发布于 2025-01-23 20:45:31 字数 314 浏览 2 评论 0原文

我的商店正在使用Coverity 2019.3。
我们已经启用了Misra-C 2004。

我想禁用Misra-C 2004规则2.2：源代码应仅使用 / * ... * /注释。

cov-Analyze命令具有禁用选项，但仅显示检查器。例如，可以使用- 禁用将其用于Misra-cast。

我们在Windows 10上使用Coverity 2019.3，其中包括IAR 8.4编译器（构建器）。

那么，如何配置覆盖率以禁用Misra-C 2004，规则2.2？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

扛起拖把扫天下 2025-01-30 20:45:31

使用- misra-config命令行选项对Coverity Misra检查进行自定义，其后是JSON-Syntax配置文件名。请参阅Synopsys文章用Misra Checker分析主源文件？

（misra_cast响应的事实 - disable是一个例外，因为它在内部的工作方式大不相同。

{ 
  version : "2.0", 
  standard : "c2004", 
  title: "Customized MISRA 2004 Compliance", 
  deviations : [ 
    {
      deviation: "Directive 2.2",
      reason: "We allow // comments here because ... ."
    }
  ]
}

禁用该规则或包含指向或引用包含基本原理的其他文件的指针。我不是Misra合规性的专家，但我的理解是Misra审计师希望看到证据表明该决定是在适当考虑系统安全的相关威胁的情况下做出的，而不仅仅是兴起或程序员方便。配置文件需要一个原因字符串，以确保很容易获得原因以满足审核。

然后添加- misra-config misra_c2004.config到cov-analyze命令行。

请注意，我没有测试上述配置文件，因为我不再可以访问该工具。请评论它是否有效，以便我可以解决此答案或删除本段。

Coverity MISRA checking is customized using the --misra-config command line option, which is followed by a JSON-syntax configuration file name. See the Synopsys article How to analyze primary source files with MISRA checkers?

(The fact that MISRA_CAST responds to --disable is an exception because, internally, it works quite differently than the others.)

For example, to disable rule MISRA 2004 2.2, create a file called, say, MISRA_c2004.config with contents:

{ 
  version : "2.0", 
  standard : "c2004", 
  title: "Customized MISRA 2004 Compliance", 
  deviations : [ 
    {
      deviation: "Directive 2.2",
      reason: "We allow // comments here because ... ."
    }
  ]
}

Ideally, the reason should explain why your organization has chosen to disable the rule or contain a pointer to or citation of some other document containing the rationale. I'm not an expert on MISRA compliance, but my understanding is a MISRA auditor would want to see evidence that the decision was made with due consideration to the relevant threats to the safety of the system, not merely on a whim or for programmer convenience. The configuration file demands a reason string in order to ensure that reason is readily available to satisfy an audit.

Then add --misra-config MISRA_c2004.config to the cov-analyze command line.

Be aware that I have not tested the above configuration file as I don't have access to the tool anymore. Please comment on whether it works so I can fix this answer or delete this paragraph.

回复收藏 0 原文