Fix some memory errors triggered by allocation failures #1995

IvanNardi · 2023-05-29T08:14:19Z

Some low hanging fruits found using nallocfuzz.
See: https://github.com/catenacyber/nallocfuzz
See: google/oss-fuzz#9902

Most of these errors are quite trivial to fix; the only exception is the stuff in the uthash.
If the insertion fails (because of an allocation failure), we need to avoid some memory leaks. But the only way to check if the HASH_ADD_* failed, is to perform a new lookup: a bit costly, but we don't use that code in any critical data-path.

example/reader_util.c

Some low hanging fruits found using nallocfuzz. See: https://github.com/catenacyber/nallocfuzz See: google/oss-fuzz#9902 Most of these errors are quite trivial to fix; the only exception is the stuff in the uthash. If the insertion fails (because of an allocation failure), we need to avoid some memory leaks. But the only way to check if the `HASH_ADD_*` failed, is to perform a new lookup: a bit costly, but we don't use that code in any critical data-path.