C/C++



  • BLAST, CODAN, cppcheck, slint, clang, something else?

    Interested:

    1. free and free

    2. Linux.

    So far, only CODAN (in Eclipse CDT from the box) and cppcheck. I've seen it on the mark, but it's about security and code corrosiveness, ideally something close to MISRA.


    CLion with his beautiful password

    I'm not asking for IDE. The analyzer is valuable to me as a utilite that Maybe IDE (then it's bonus), but Duty. Work alone.

    As for the beauty of the passer at CLion. Yeah, on the test run, he found a few plugs:

    1. Data flow analysis: File is too complex to perform context-sensitive data-flow analysis (at line 11)Hi.)
    2. Type checks: Parameter type mismatch: Values of type 'size_t' may not fit into the receiver type 'int' at line 267second argument fgets())
    3. Unused code: Unused import statement at line 9was the inclusion of unnecessary .h)

    Kind of helpful. But he is. I didn't find the chief.:

    cppcheck: (error) Memory leak: src (at line 249)
    

    I specifically commented on the challenge. free()And not straight, but through the srapper, that the sppcheck has been very good. CODAN did it, too. CLion, no. So he's far away from perfection. Not to mention the total lack of normal support for valgrind. ♪ ♪ )

    Not that a separate analyzer, but clang at the maximum barning level is a pretty useful thing.

    Any examples? I had nothing to do with him, and I don't really know what the difference is:

    gcc -Wall -pedantic -pedantic-errors
    


  • It's now under Linux. http://www.viva64.com/ru/pvs-studio-download-linux/ which can even be http://www.viva64.com/ru/b/0457/ ♪ It's actually a good thing.




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2