c-ares

811 Commits

14 Branches

96 Tags

22 MiB

Tag: Branch: Tree: coverity_scan

Commit Graph

Author	SHA1	Message	Date
Brad House	16f217cd64	Move FUZZING.md to the top level Though the fuzzing tests are in the tests directory, we should move the FUZZING.md file itself to the toplevel to make it more visible. Signed-off-by: Brad House (@bradh352)	3 months ago
Brad House	fb3160f375	Fuzzing: Fix memory leak in test case The test case changes introduced a memory leak in the test itself (not in c-ares). Fix this memory leak. Also move prior fuzzing information into the new fuzzing document. Fix By: Brad House (@bradh352)	3 months ago
Brad House	bb9c616d03	Fuzzing: add fetcher/writers to fuzzing suite The coverage of the fuzzer is fairly low as it was only testing the parsing, not trying to read the data from the datastructure or writing it back out as a DNS message. Lets extend, and also provide a FUZZING.md to help people new to fuzzing get up and running. Authored-By: Brad House (@bradh352)	3 months ago

Author

SHA1

Message

Date

Brad House

16f217cd64

Move FUZZING.md to the top level

Though the fuzzing tests are in the tests directory, we should move
the FUZZING.md file itself to the toplevel to make it more visible.

Signed-off-by: Brad House (@bradh352)

3 months ago

Brad House

fb3160f375

Fuzzing: Fix memory leak in test case

The test case changes introduced a memory leak in the test itself
(not in c-ares).  Fix this memory leak.  Also move prior fuzzing
information into the new fuzzing document.

Fix By: Brad House (@bradh352)

3 months ago

Brad House

bb9c616d03

Fuzzing: add fetcher/writers to fuzzing suite

The coverage of the fuzzer is fairly low as it was only testing the
parsing, not trying to read the data from the datastructure or writing
it back out as a DNS message.  Lets extend, and also provide a
FUZZING.md to help people new to fuzzing get up and running.

Authored-By: Brad House (@bradh352)

3 months ago

1 Commits (coverity_scan)