-
Notifications
You must be signed in to change notification settings - Fork 122
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
Recursion causes stack overflow which aborts process #121
Comments
Thanks, I will take a look. |
Should be good now. |
Updated my checkout and re-ran the fuzzer, got this crash. Want me to move this to a new issue and close this one? |
No, here is fine... |
I can reproduce that there are stack overflows .. sigh. |
Added more anti-recursion measures. |
Okay, cool. I'll let the fuzzer run on this for a few hours and then call it good enough to close this, then I'll start running the fuzzer without ignoring panics and open bugs for those. |
Hmm... I can get the fuzzer to abort on a stack overflow... somewhere. But it doesn't want to tell me where. Fun.
Am trying to get it to reproduce with a sanitizer enabled, which hopefully will get it to exit cleanly enough to write an artifact and tell me what the failing file is. |
that is fixed as well |
and fixed |
Okay, a few hours of 12 cores fuzzing it can't find anything. I'll mark this as done, and continue fuzzing without the "ignore panics" bit. If any stack overflows come up then, I can just file normal bugs for it. |
Since this thread seems to be about crashing the code, here are nice example files: https://github.com/pdf-association/safedocs/tree/main/Miscellaneous%20Targeted%20Test%20PDFs |
Trying to parse the following pdf contained within the zip file will cause a stack overflow.
The fuzzing harness I used to find this was modified from the existing one, since there's already lots of panics and I wanted to look for more interesting bugs.
crash.zip
The text was updated successfully, but these errors were encountered: