Zbigniew Jędrzejewski-Szmek e2093454a2 shared/specifier: be less extravagant with memory allocations ... ubsan times out because we do too many allocations: $ valgrind build/fuzz-unit-file test/fuzz-regressions/fuzz-unit-file/oss-fuzz-6977-full ... test/fuzz-regressions/fuzz-unit-file/oss-fuzz-6977-full... ok ==1757== ==1757== HEAP SUMMARY: ==1757== in use at exit: 0 bytes in 0 blocks ==1757== total heap usage: 199,997 allocs, 199,997 frees, 90,045,318,585 bytes allocated ... ==3256== total heap usage: 100,120 allocs, 100,120 frees, 13,097,140 bytes allocated https://oss-fuzz.com/v2/issue/4651449704251392/6977 should now be really fixed. e3c3d6761b was the first attempt, but even with this change, e3c3d6761b still makes sense.		2018-03-28 10:38:45 +02:00
..
fuzz-dns-packet	test: run all fuzz regression tests with all sanitizers	2018-03-14 14:27:04 +01:00
fuzz-unit-file	shared/specifier: be less extravagant with memory allocations	2018-03-28 10:38:45 +02:00
.gitattributes	Add .gitattributes for test/fuzz-regressions	2018-03-17 09:01:53 +01:00
meson.build	core/load-fragment: reject overly long paths early	2018-03-21 00:46:13 +01:00