Open nathaniel-brough opened 10 months ago
Neat!
Looks like its coming from here: https://github.com/facebook/relay/blob/0a9d473edeee122b1837d579b4e2268c5b2cd641/compiler/crates/graphql-syntax/src/lexer.rs#L171
Maybe we need some way to propagate this error state up to the parent lexer. Looks like logos can return a result type from the callback?
Seems reasonable. I'm not familiar with the logos crate, though it looks pretty nice. It'll take me a little while to get up to speed, in terms of understanding the code well enough to do bugfixes. Ironically it's easier to write a fuzzer than it is to understand the code that you are fuzzing. If you don't get to it in the meantime, I'll start looking into bug-fixes next week. But I'll ping here before I start :)
NOTE: This bug report is part of a trial for using fuzz-harnesses, see https://github.com/facebook/relay/issues/4566#issuecomment-1883491254 for more context. This bug was found using the fuzz harness in #4565.
Steps to reproduce
My approximation of the information that you'll get from google/oss-fuzz if this where integrated.
Stacktrace and error input
Crash file
OSS-fuzz will automatically minimise the test-case so there is no need to run
cargo fuzz tmin
. crash-3fc82c59c003bc1e84d1fc3bbc47019819f1ecac.txtTo reproduce using cargo fuzz simply run;