# The rule c:S836 seems not to work

**URL:** <https://community.sonarsource.com/t/the-rule-c-s836-seems-not-to-work/69422>\
**Category:** VS Code\
**Tags:** cfamily, sonarqube-ide, sonarqube\
**Created:** [August 7, 2022, 1:50pm UTC](https://community.sonarsource.com/t/the-rule-c-s836-seems-not-to-work/69422 "2022-08-07T13:50:37Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![zhangjiuwang](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/zhangjiuwang/32/32271_2.png) [@zhangjiuwang](https://community.sonarsource.com/u/zhangjiuwang)\
**Post date:** [August 9, 2022, 3:41pm UTC](https://community.sonarsource.com/t/the-rule-c-s836-seems-not-to-work/69422/6 "2022-08-09T15:41:17Z")

</div>

In the original post ,I build it on Windows ,it reports Exit code != 0 when analysis. same as

[ExitCode!=0](https://community.sonarsource.com/t/com-sonar-cpp-analyzer-analyzer-analyzerexception-exit-code-0/42048)

In the second example,I build it on Ubantu. Analysis works well。

I want to know whether this issue is being processed. It seems that it has not been allocated since its creation.

---

_[View the full topic](https://community.sonarsource.com/t/the-rule-c-s836-seems-not-to-work/69422)._