8ba9e8cf63
Descriptions are taken from the files themselves or READMEs. Description followed by a space with the language in marked up as code. Change-Id: I5f91e85d1034736289aedf27de00df00db3ff19c Signed-off-by: Tom Hiller <thrilleratplay@gmail.com> Reviewed-on: https://review.coreboot.org/27563 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> |
||
|---|---|---|
| .. | ||
| jpeg-test-cases | ||
| Makefile | ||
| README | ||
| description.md | ||
| jpeg-test.c | ||
README
Fuzz tests ========== make run (with afl-fuzz installed) takes a real long time and creates test cases in jpeg-results/ that crash the jpeg code. These test cases can then be used to gdb the test app and dig into the decoder to fix the issues. This is mostly a proof of concept because the jpeg code isn't used very often (only for splash screens). However there are other regions in coreboot that could benefit from similar treatment.