bf966f5237
It was not possible to disable alpha.unix.cstring.OutOfBounds checker's reports since unix.Malloc checker always implicitly enabled the filter. Moreover if the checker was disabled from command line (-analyzer-disable-checker ..) the out of bounds warnings were nevertheless emitted under different checker names such as unix.cstring.NullArg, or unix.Malloc. This patch fixes the case sot that Malloc checker only enables implicitly the underlying modeling of strcpy, memcpy etc. but not the warning messages that would have been emmitted by alpha.unix.cstring.OutOfBounds Patch by: Dániel Krupp Differential Revision: https://reviews.llvm.org/D48831 llvm-svn: 337000
23 lines
729 B
C
23 lines
729 B
C
// RUN: rm -f %t
|
|
// RUN: %clang_analyze_cc1 -fblocks -analyzer-checker=core,unix.Malloc,unix.cstring.NullArg -analyzer-disable-checker=alpha.unix.cstring.OutOfBounds -analyzer-output=plist -analyzer-config path-diagnostics-alternate=false -o %t %s
|
|
// RUN: FileCheck -input-file %t %s
|
|
|
|
typedef __typeof(sizeof(int)) size_t;
|
|
void *malloc(size_t);
|
|
void free(void *);
|
|
char *strncpy(char *restrict s1, const char *restrict s2, size_t n);
|
|
|
|
|
|
|
|
void cstringchecker_bounds_nocrash() {
|
|
char *p = malloc(2);
|
|
strncpy(p, "AAA", sizeof("AAA")); // we don't expect warning as the checker is disabled
|
|
free(p);
|
|
}
|
|
|
|
// CHECK: <key>diagnostics</key>
|
|
// CHECK-NEXT: <array>
|
|
// CHECK-NEXT: </array>
|
|
// CHECK-NEXT: </dict>
|
|
// CHECK-NEXT: </plist>
|