Zbigniew Jędrzejewski-Szmek ec6bda56cb bus-message: avoid an infinite loop on empty structures ... The alternative would be to treat gvariant and !gvariant messages differently. But this is a problem because we check signatures is variuos places before we have an actual message, for example in sd_bus_add_object_vtable(). It seems better to treat things consistent (i.e. follow the lowest common denominator) and disallow empty structures everywhere.		2018-10-02 11:53:20 +02:00
..
fuzz-bus-message	bus-message: avoid an infinite loop on empty structures	2018-10-02 11:53:20 +02:00
fuzz-dhcp-server
fuzz-dhcp6-client	fuzz: unify the "fuzz-regressions" directory with the main corpus	2018-10-02 09:41:25 +02:00
fuzz-dns-packet	fuzz: unify the "fuzz-regressions" directory with the main corpus	2018-10-02 09:41:25 +02:00
fuzz-journal-remote	fuzz: unify the "fuzz-regressions" directory with the main corpus	2018-10-02 09:41:25 +02:00
fuzz-journald-syslog	fuzz: unify the "fuzz-regressions" directory with the main corpus	2018-10-02 09:41:25 +02:00
fuzz-ndisc-rs	fuzz: unify the "fuzz-regressions" directory with the main corpus	2018-10-02 09:41:25 +02:00
fuzz-unit-file	fuzz: unify the "fuzz-regressions" directory with the main corpus	2018-10-02 09:41:25 +02:00
.gitattributes
meson.build	meson: treat all fuzz cases as unit tests	2018-10-02 09:42:19 +02:00