search for: llvmfuzzerinitialize

...ker to allow // weak symbols to be undefined. That is a complication we don't want to expose // to clients right now. That makes sense, but with current implementation, you cannot use libFuzzer's interface functions other than LLVMFuzzerTestOneInput. Below is a small example to verify that LLVMFuzzerInitialize is not being called on Mac: #include <stddef.h> #include <stdint.h> #include <stdio.h> extern "C" int LLVMFuzzerInitialize(int* argc, char*** argv) { printf("Hello from LLVMFuzzerInitialize, argc: %i\n", *argc); return *argc; } extern "C" int L...

...> I have the same problem with clang-proto-fuzzer, which uses the same approach with flags as llvm-isel-fuzzer. The solution I was thinking about is (drum roll!) to encode the flags in the binary name, e.g. "./llvm-isel-fuzzer,-flag1,-flag2" and then read these flags from argv[0] in LLVMFuzzerInitialize() Then in oss-fuzz build.sh we will just do this: for flags in -flag1a,-flag1b -flag2a,-flag2b; do cp llvm-isel-fuzzer $OUT/llvm-isel-fuzzer,$flags done > > > Who else wants to be automatically CC-ed to all trophies? > > (I'll need to add your e-mail here: > > https://...

On Tue, Aug 22, 2017 at 4:34 PM, Kostya Serebryany <kcc at google.com> wrote: > > > On Tue, Aug 22, 2017 at 4:21 PM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> Hi, >> >> As a part of a recent move of libFuzzer from LLVM to compiler-rt I am >> looking into updating the build code >> for the libraries which use libFuzzer.