h264parse: do not use _unchecked bytewriter variants to insert config
authorMark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Fri, 6 Apr 2012 12:23:53 +0000 (14:23 +0200)
committerMark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Fri, 6 Apr 2012 12:35:56 +0000 (14:35 +0200)
commit0882adc69f7a3e420c56f5ba8c4cabb942e285b8
tree3f568500f4fde818ee224c8c3911aba638ae1ff6
parent70056a37c47d085c917f94574b76afb8c5f707dc
h264parse: do not use _unchecked bytewriter variants to insert config

.. since the bytewriter is explicitly created with non-fixed size to
allow (very much so expected) growth.

Partially reverts commit 20669d461a4953eb5ed01374d5ab628b4dc73b64 while
trying to keep (some?) compilers happy.

IIRC, the purpose of GstByteWriter in the first place was (at least)
being able to dump data without having to fuss with memory expansion
and size issues ...

Fixes #673485.
gst/h264parse/gsth264parse.c
gst/videoparsers/gsth264parse.c