-
Notifications
You must be signed in to change notification settings - Fork 18
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
Grammar mutator issue : _pick_non_term_node #35
Comments
How do you generate the corpus (i.e., files in The error might be thrown from here: Grammar-Mutator/src/tree_mutation.c Lines 202 to 209 in cbe5e32
|
I am also trying to fuzz javascript using Grammar Mutator and a customised grammar file. The process starts off great but within a day or two I perpetually run into the fuzzer crashing as described here. In my case I am not adding any additional test cases other than the trees generated by Grammar Mutator and am at a loss as to what is going wrong. From what I can see; only the mater process is crashing for me. |
try and run with a new empty output directory and an input directory generated from the |
I ran into the same bug. The fuzzing started great, but then after 22 minutes it crashed:
The seed inputs were generated using the provided generator: The following is the current input as saved by AFL in
Thanks. |
Another crash:
Current input:
|
This can happen if you neglect to include the start node; happened to me by accident once, went away right away once I put it back. |
I'm also hitting this issue:
This is because indeed the grammar tree is missing from |
I'm struggling with the same issue while trying to use Grammar-Mutator from AFL with a preexisting source-based corpus. (Note: using source-based seeds works when running the built-in generator like |
Hello .
When running Grammar mutator on a target, there is a problem right before running AFL++ on the target .
Here is the log :
_pick_non_term_node returns NULL: No such file or directory
Flags :
Ubuntu 20.04
AFL++ 4.00
Any ideas ?
The text was updated successfully, but these errors were encountered: