Ivan Fratric

Interesting. I actually created a clean Windows 7 32-bit VM to test it, updated it, built TinyInst and, as far as I can tell, everything is working normally. Running `litecov.exe...

Hi! It's certainly possible to hit OOM if the samples are large and the corpus keeps growing. However, I'm curious if you can share more about your setup (either here...

Thanks for reviewing the code :) "Can jackalope run without inputs?" Not sure what you mean, did you mean *with* inputs. Because in the grammar fuzzing mode, it's actually expected...

There are actually several reasons why this might happen. Let me explain what it takes for the sample to be "interesting". When Jackalope processes a sample and it triggers new...

Note that different coverage for each run is fine, but there needs to be at least one coverage offset that is seen in all the runs with the sample.

Looks like the sample you provided caused a crash in the target so it didn't get added to the corpus (hence the error message you are getting). If the sample...

If you post your full command line I might be able to tell you more.

Hmm yes, I don't see anything wrong in the command line itself. If you're getting errors, you might try without -cmp_coverage or with -patch_return_addresses, and see if that behaves differently.

Exec speed, code coverage, no of paths should all be printed to the stdout every second. I guess if your target prints out a lot of stuff it might fly...

The percentage is, by design, not known. TinyInst is a dynamic instrumentation and it discovers offsets at runtime, it doesn't know their count in advance. If you want an estimate...