On Sat, Jan 10, 2015 at 6:00 PM, wm4 nfx...@googlemail.com wrote:
With a certain fuzzed file, the parser will always return 0 consumed
bytes, which makes calling code call the parser infinitely. Return the
full packet size on error instead. (Here it would be nice if parsers
could return
On Sat, 10 Jan 2015 18:03:48 +0100
Hendrik Leppkes h.lepp...@gmail.com wrote:
On Sat, Jan 10, 2015 at 6:00 PM, wm4 nfx...@googlemail.com wrote:
With a certain fuzzed file, the parser will always return 0 consumed
bytes, which makes calling code call the parser infinitely. Return the
full
With a certain fuzzed file, the parser will always return 0 consumed
bytes, which makes calling code call the parser infinitely. Return the
full packet size on error instead. (Here it would be nice if parsers
could return errors at all.)
Additionally, _if_ there's some data left, return that too,
On Sat, Jan 10, 2015 at 01:21:42PM -0500, Ronald S. Bultje wrote:
Hi,
On Sat, Jan 10, 2015 at 12:15 PM, wm4 nfx...@googlemail.com wrote:
On Sat, 10 Jan 2015 18:03:48 +0100
Hendrik Leppkes h.lepp...@gmail.com wrote:
On Sat, Jan 10, 2015 at 6:00 PM, wm4 nfx...@googlemail.com wrote:
Hi,
On Sat, Jan 10, 2015 at 12:15 PM, wm4 nfx...@googlemail.com wrote:
On Sat, 10 Jan 2015 18:03:48 +0100
Hendrik Leppkes h.lepp...@gmail.com wrote:
On Sat, Jan 10, 2015 at 6:00 PM, wm4 nfx...@googlemail.com wrote:
With a certain fuzzed file, the parser will always return 0 consumed
