Tim-Philipp Müller 69c8d994e4 bytereader: fix peek value when scanning for 00 00 01 with non-0 offset ... We would add the offset a second time in _scan_for_start_code() when we found a result, but it's already been added to the data pointer at the beginning of _masked_scan_uint32_peek(), so the peeked value would be wrong if the initial offset was >0, and we would potentially read memory out-of-bounds. Add unit test for all of this. https://bugzilla.gnome.org/show_bug.cgi?id=778365		2017-02-23 12:06:59 +02:00
..
elements	queue2: Fix watermark test	2016-09-17 10:00:34 +01:00
generic	check: Rename states unit test	2015-08-14 11:10:37 +02:00
gst	datetime: fix potential out-of-bound read on malformed datetime string	2017-01-15 11:54:13 +00:00
libs	bytereader: fix peek value when scanning for 00 00 01 with non-0 offset	2017-02-23 12:06:59 +02:00
pipelines	tests: parse-launch: looks clean nowadays, so re-enable for valgrind	2016-09-26 12:12:12 +01:00
tools	tests: refactor tools check a little	2014-10-31 16:10:01 +00:00
.gitignore	tests: add check for gst-inspect --exists functionality	2012-09-01 23:02:10 +01:00
Makefile.am	tests: parse-launch: looks clean nowadays, so re-enable for valgrind	2016-09-26 12:12:12 +01:00
meson.build	meson: Make use of new environment object and set plugin path to builddir	2016-10-14 17:30:00 +02:00