Catherine
Catherine
I think the new global_allocator attribute (RFC 1974) took care of it. Can you recheck?
@brayniac would you be willing to build rustc and LLVM from scratch if I provided you with an LLVM patch?
Seems similar to #15.
One reason coverage may not be increasing is that libfuzzer is expecting instruction profiler instrumentation (the equivalent of `clang -fprofile-instr-generate`). This requires explicit frontend support. Right now, even with the...
Yeah, pretty sure my comment above in correct. Pending changes in rustc this won't work.
This may not necessarily be desirable because building unsafe code with `opt-level = 0` is likely to leave more (most, though not all) dynamically reachable UB as it is. But...
Or perhaps we could leave profiles alone and just mention the `cargo fuzz run foo --release` invocation in README. Though it ought to be obvious to anyone with even little...
Triage: documentation issue, excerpt from above: > rust-san has instructions for setting up an instrumented stdlib with xargo, we could probably just provide links to that and perhaps add a...
I hit that all the time (this is a standard problem if you build LLVM with Clang); fortunately, with master avoiding it as simple as `CXX_FLTO_FLAGS= LD_FLTO_FLAGS= python3.5 setup.py build`...
Why a file and not a string?