Michael Jones

Apologies for the delay This CI run reproduces the issue: https://github.com/TheOpenSpaceProgram/osp-magnum/runs/5082236623?check_suite_focus=true#step:7:137 Looks like it only happens when we include the file in one of our cpp files, and only with...

I totally get where you are coming from. The clang analyzer does have false positives sometimes. In my opinion, it would be good enough to just add the annotation comments...

I did manage to cut most 3rd party code out of my analysts by only generating a compiler-commands.json file for my first-party source files. Here's how I did it: https://github.com/TheOpenSpaceProgram/osp-magnum/blob/master/.github/workflows/analyzers.yml

Were there plans to make a release in 2021 still? I'm not in any particular need of one, I just prefer to use official release when possible instead of some...

Understood! Thanks for the explanation. I'm not in a rush, so no big deal to me.

> On newer Windows versions, you should also grab a more recent DynamoRIO version from https://github.com/DynamoRIO/dynamorio/releases and rebuild WinAFL with it. Is there a release of Dynamorio newer than 8.0.0-1...

> I guess it's possible that the fuzz() got inlined in main(). Ok. To eliminate the possibility of function inlining, I've re-written my app as such: main.cpp ```cpp extern "C"...

I've "updated" to the newest weekly build of DynamoRIO-Windows-8.0.18705 Recompiled: ```powershell &'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe' -G"Visual Studio 16 2019" -A x64 -S .\winafl\ -B .\build-winafl\ -DDynamoRIO_DIR=C:\users\mjones\DynamoRIO-Windows-8.0.18705\cmake &'C:\Program Files (x86)\Microsoft...

> > > There also seems to be an error with your command line: > > ``` > .\afl-fuzz.exe -D C:\Users\mjones\DynamoRIO-Windows-8.0.18705\bin64 -i testin -o testout -t 200000 -- -coverage_module minimal_fuzzer_w64d_1_0...

> > Visual Studio 2017 Why are you using VS2017? That's 4 years old.