C++/clang analyzer memory leaks?

Question

I'm trying to get clang++ to tell me there is a memory leak. I tried scan-build but it reported nothing. How do I get llvm/clang to warn me of this problem?

#include <iostream>

int main() {
        int *a = new int;
        *a = 8;
        std::cout<< a << std::endl;
}

Memory allocated with malloc is reported for me, but not if I use `new`. E.g.: `int *a = (int*)malloc(sizeof(int));` — dmitri, Oct 03 '13 at 02:46
Possibly dup: http://stackoverflow.com/questions/3455157/example-code-to-trigger-clangs-static-analyser — prehistoricpenguin, Oct 03 '13 at 03:14
possible duplicate of [clang analyzer memory leaks](http://stackoverflow.com/questions/19149002/clang-analyzer-memory-leaks) — Benjamin Bannier, Sep 06 '15 at 18:30

score 0 · Answer 1 · answered Oct 03 '13 at 20:03

0

False-positive pruning usually leads to removing all leaks that originate from main(), since the program will exit anyway. Try analyzing the same code, but in a different function.

answered Oct 03 '13 at 20:03

Michael Donohue

11,776
5
31
44

Leaking pointer allocated with new in a non `main` function is not reported for me either. There is [unix.Malloc check](http://clang-analyzer.llvm.org/available_checks.html) I can't find anything related to `new` check. Static analysis just doesn't cover everything. The reason why dynamic analysis with dtrace or other tools exists. – dmitri Oct 07 '13 at 22:57

score 0 · Answer 2 · answered Mar 14 '14 at 08:07

0

Because int is too small, there is something like one "reserved section" for program so for small object no need to extend memory area, try to apply 1024 * 1024 * 10 then check the result

answered Mar 14 '14 at 08:07

http8086

1,306
16
37

C++/clang analyzer memory leaks?

2 Answers2

Linked