-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
slice bounds out of range in decode #26
Comments
This should come up easily with fuzzing if you want to go that route. The regular decode routine has been fuzzed pretty heavily. |
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. |
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. |
Good point. I did not. I was focusing on the asm core. I'll fuzz the framing reader Monday. |
You might not need to. I think there's an obvious bug. Code coming... |
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. |
Thanks for the fix. And yes the files were corrupt! |
I fuzzed NewReader()/Read() for several billion iterations and didn't find anything. Final line before ^C: |
I'm trying to get a full working repro, but my current best guess is this was while trying to read a file which had experienced a partial write of the compressed data:
The text was updated successfully, but these errors were encountered: