mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-12-14 19:49:36 +00:00
50e0372f82
I.e. not after. In the c++-allocator-inlining=true mode, we need to make the assumption that the conservatively evaluated operator new() has returned a non-null value. Previously we did this on CXXNewExpr, but now we have to do that before calling the constructor, because some clever constructors are sometimes assuming that their "this" is null and doing weird stuff. We would also crash upon evaluating CXXNewExpr when the allocator was inlined and returned null and had a throw specification; this is UB even for custom allocators, but we still need not to crash. Added more FIXME tests to ensure that eventually we fix calling the constructor for null return values. Differential Revision: https://reviews.llvm.org/D42192 llvm-svn: 323370
27 lines
595 B
C++
27 lines
595 B
C++
// RUN: %clang_analyze_cc1 -w -analyzer-checker=core,debug.ExprInspection -analyzer-config c++-allocator-inlining=true -std=c++11 -verify %s
|
|
|
|
void clang_analyzer_eval(bool);
|
|
|
|
typedef __typeof__(sizeof(int)) size_t;
|
|
|
|
|
|
// These are ill-formed. One cannot return nullptr from a throwing version of an
|
|
// operator new.
|
|
void *operator new(size_t size) {
|
|
return nullptr;
|
|
}
|
|
void *operator new[](size_t size) {
|
|
return nullptr;
|
|
}
|
|
|
|
struct S {
|
|
int x;
|
|
S() : x(1) {}
|
|
~S() {}
|
|
};
|
|
|
|
void testArrays() {
|
|
S *s = new S[10]; // no-crash
|
|
s[0].x = 2; // expected-warning{{Dereference of null pointer}}
|
|
}
|