search for: asan_malloc

First off, thanks -- this is a pretty great library and it feels like I'm learning a lot. I'm getting some more experience with libfuzzer and finding that I have a couple of questions: - How does libfuzzer decide to write a new test file? What distinguishes this one from all the other cases for which new test inputs were not written? Must be something about the path taken through the

...ue, cleared=false, alignment=8, size=<optimized out>, cache=0x7f76e1bd80c8, this=0x192db80 <__asan::instance>) #8 Allocate (can_fill=true, alloc_type=__asan::FROM_MALLOC, stack=0x7fffd956a360, alignment=8, size=<optimized out>, this=0x192db80 <__asan::instance>) #9 __asan::asan_malloc (size=size at entry=4096, stack=stack at entry=0x7fffd956a360) at /home/brian/tmp/testing/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_allocator.cc:718 #10 0x00000000004da852 in __interceptor_malloc (size=4096) at /home/brian/tmp/testing/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_malloc_l...