search for: can_fill

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

...d at entry=33) #6 0x000000000044747e in Allocate (class_id=33, allocator=0x192db80 <__asan::instance>, this=0x7f76e1bd80c8) #7 Allocate (check_rss_limit=true, 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...