You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really need to come up with an easier way for us to import fuzz crash reports into the project. On this one, it looks like this might be a test failure? The data appears to fail deserialization due to valid errors in the stream. I thought the fuzzing impl dealt with that. I'll have to take a look.
Ah, I see, this appears to be a round-tripping issue. I wonder if that's ultimately important or not for us... I'm not sure it's catching what we are most concerned with fuzz, which is bad data coming in off the wire and crashing the deserialization or causing issues at that time. The fuzz target seems to trip up on this round-trip logic often, and I'm not sure if it's an important detail. That is, this is bad data, it shouldn't be valid to construct it...
Running cargo-fuzz in this repo with #2025 PR included there's a crash:
The payload:
The text was updated successfully, but these errors were encountered: