slice bounds out of range in decode about snappy HOT 8 CLOSED

This should come up easily with fuzzing if you want to go that route.

The regular decode routine has been fuzzed pretty heavily.

from snappy.

Any update on getthig this data? I ran several billion fuzzed cases through the asm decoder and the Go one with no mismatch in behaviour or panics.

from snappy.

Did you fuzz the Reader type as well as the Decode function? The bug might be in the framing format decoder, not in the core decoder.

from snappy.

Good point. I did not. I was focusing on the asm core. I'll fuzz the framing reader Monday.

from snappy.

You might not need to. I think there's an obvious bug. Code coming...

from snappy.

I'm calling this bug fixed, but I think that your compressed files are still corrupt somehow. It's just that the corruption should now return an error instead of panic.

from snappy.

Thanks for the fix. And yes the files were corrupt!

from snappy.

I fuzzed NewReader()/Read() for several billion iterations and didn't find anything.

Final line before ^C:
2016/04/05 10:00:47 slaves: 28, corpus: 220 (19h19m ago), crashers: 0, restarts: 1/10000, execs: 6920725600 (84639/sec), cover: 154, uptime: 22h42m

from snappy.