luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-26 23:46:15 +01:00
Code Issues Packages Projects Releases Wiki Activity
e2d3349c56
glib/fuzzing
History
Marc-André Lureau 591d8676ee uri: modify g_uri_parse_params() to take flags 
This will allow to further enhance the parsing, without breaking API,
and also makes argument on call side a bit clearer than just TRUE/FALSE.

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2020-07-07 15:16:22 +04:00
..
driver.c Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_bookmark.c Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_bookmark.corpus Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_dbus_message.c Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_key.c Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_key.corpus Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_uri_escape.c fuzzing: Test g_uri_unescape_segment() as well as g_uri_unescape_bytes() 2020-07-01 13:28:09 +01:00
fuzz_uri_parse_params.c uri: modify g_uri_parse_params() to take flags 2020-07-07 15:16:22 +04:00
fuzz_uri_parse.c fuzzing: Test URI parsing with and without the strict flag 2020-06-30 11:10:51 +01:00
fuzz_variant_binary.c Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_variant_text.c Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz_variant_text.dict Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
fuzz.h Integrate oss-fuzz targets 2018-10-11 00:02:03 +00:00
meson.build fuzzing: Add fuzz tests for GUri parsing and escaping 2020-06-25 13:57:35 +04:00
README.md Fix oss-fuzz coverage link 2020-02-15 08:23:25 +00:00

README.md

Fuzz targets used by oss-fuzz.

Useful links: Dashboard (requires access), Build logs, Coverage

How to add new targets

Add fuzz_target_name.c and edit meson.build accordingly.

New targets are picked up by oss-fuzz automatically within a day. Targets must not be renamed once added.

Add (optional) fuzz_target_name.dict containing keywords and magic bytes.

Add (optional) fuzz_target_name.corpus with file names on separate lines. Wildcards ?, * and ** are supported. Examples below.

glib/*  # all files in directory glib
glib/** # all files in directory glib and sub-directories
**.xbel # all files ending with .xbel in the repository

Recommended reading: Fuzz Target, Dictionaries, Corpus

How to reproduce oss-fuzz bugs locally

Build with at least the following flags, choosing a sanitizer as needed. A somewhat recent version of clang is recommended.

$ CC=clang CXX=clang++ meson DIR -Db_sanitize=<address|undefined> -Db_lundef=false

Afterwards run the affected target against the provided test case.

$ DIR/fuzzing/fuzz_target_name FILE

FAQs

What about Memory Sanitizer (MSAN)?

Correct MSAN instrumentation is difficult to achieve locally, so false positives are very likely to mask the actual bug.

If need be, you can still reproduce those bugs with the oss-fuzz provided docker images.

There are no file/function names in the stack trace.

llvm-symbolizer must be in PATH.

UndefinedBehavior Sanitizer (UBSAN) doesn't provide a stack trace.

Set environment variable UBSAN_OPTIONS to print_stacktrace=1 prior to running the target.