mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-29 09:36:05 +00:00
e3377fbca2
This fixes an issue pointed to by Jordan: if unix.Malloc and unix.MismatchedDeallocator are both on, then we end up still tracking leaks of memory allocated by new. Moved the guards right before emitting the bug reports to unify and simplify the logic of handling of multiple checkers. Now all the checkers perform their checks regardless of if they were enabled, or not, and it is decided just before the emitting of the report, if it should be emitted. (idea from Anna). Additional changes: improved test coverage for checker correlations; refactoring: BadDealloc -> MismatchedDealloc llvm-svn: 178814
29 lines
801 B
C++
29 lines
801 B
C++
// RUN: %clang_cc1 -analyze -analyzer-checker=core,unix.Malloc,unix.MismatchedDeallocator -analyzer-store region -std=c++11 -verify %s
|
|
// expected-no-diagnostics
|
|
|
|
typedef __typeof(sizeof(int)) size_t;
|
|
void *malloc(size_t);
|
|
void free(void *);
|
|
|
|
//--------------------------------------------------------------------
|
|
// Check that unix.Malloc + unix.MismatchedDeallocator does not enable
|
|
// warnings produced by the alpha.cplusplus.NewDelete checker.
|
|
//--------------------------------------------------------------------
|
|
void testNewDeleteNoWarn() {
|
|
int i;
|
|
delete &i; // no-warning
|
|
|
|
int *p1 = new int;
|
|
delete ++p1; // no-warning
|
|
|
|
int *p2 = new int;
|
|
delete p2;
|
|
delete p2; // no-warning
|
|
|
|
int *p3 = new int; // no-warning
|
|
|
|
int *p4 = new int;
|
|
delete p4;
|
|
int j = *p4; // no-warning
|
|
}
|