-
Notifications
You must be signed in to change notification settings - Fork 12
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
Echidna manual seed in debug mode #24
Comments
I'm not quite sure to understand why we would like to log the seed when running in debug mode? If users want to debug, they can also specify the seed through the command line. |
My thought was that when debugging sometimes you'll run into an unexpected (non-deterministic) error, which can be annoying to reproduce. If we have |
Mmmh I see. The thing is that unless the user specifies a specific seed to use by Echidna we will use a different seed at every fuzzing iteration, so we'll have to record all of them for reproducibility. I guess instead of relying on Echidna manually generating a seed we can generate random seeds (if I'm also wondering wether we should make |
A potential problem with having One solution could be that all seeds passed to Echidna are generated by a single input from |
Randomly generate (and log) a seed for Echidna to use when fuzzing for new input in debug mode so that behaviour can be reproduced in testing?
i.e. when we invoke Echidna through
hybrid-echidna
, we should pass the--seed <value>
parameter through on the "cli", where<value>
is a seed we generate internally, but only in debug mode.The text was updated successfully, but these errors were encountered: