e144b72372
Summary: I know of two implementations that do this (ASan is not protecting against accessing the returned memory for now, just like malloc(0)): SIE libc on the PS4 dlmalloc has a flag for this This allows us to properly support this behaviour. Reviewers: vsk, kcc Subscribers: llvm-commits, kubamracek Differential Revision: https://reviews.llvm.org/D31295 llvm-svn: 299016
22 lines
708 B
C++
22 lines
708 B
C++
// RUN: %clangxx_asan -O0 %s -o %t
|
|
// Default is true (free on realloc to 0 size)
|
|
// RUN: %run %t 2>&1 | FileCheck %s
|
|
// RUN: %env_asan_opts=allocator_frees_and_returns_null_on_realloc_zero=true %run %t 2>&1 | FileCheck %s
|
|
// RUN: %env_asan_opts=allocator_frees_and_returns_null_on_realloc_zero=false %run %t 2>&1 | FileCheck %s --check-prefix=NO-FREE
|
|
|
|
#include <stdio.h>
|
|
#include <stdlib.h>
|
|
|
|
int main() {
|
|
void *p = malloc(42);
|
|
p = realloc(p, 0);
|
|
if (p) {
|
|
// NO-FREE: Allocated something on realloc(p, 0)
|
|
fprintf(stderr, "Allocated something on realloc(p, 0)\n");
|
|
} else {
|
|
// CHECK: realloc(p, 0) returned nullptr
|
|
fprintf(stderr, "realloc(p, 0) returned nullptr\n");
|
|
}
|
|
free(p);
|
|
}
|