Hacker News Reader

Comment by xhrpost | Hacker News Reader

Anyone having any luck compiling libjpeg-turbo with instrumentation?

This configuration command prior to make worked for me on Linux:

    ./configure --disable-shared CC="afl-gcc"

It calls the AFL GCC compiler instead, which presumably injects instrumentation.

Thanks! Got that part working. How can you tell if djpeg exits 0 for a given queue item?

I'm not sure if it's required (to know the exit code). inputs, both valid and invalid, will activate various paths in djpeg/libjpeg, and that's the basic goal here.

In case you'd like to test persistent fuzzing (should be faster due to a few factors), you can try modifying https://github.com/google/honggfuzz/blob/master/examples/lib... - it will probably take creating main() func which will read data in the AFL_LOOP() loop and call LLVMFuzzerTestOneInput with that input.

My goal with the exit code is that (I think) an exit of 0 would mean that a valid JPEG image was found.

Reply on news.ycombinator.com