LibAFL icon indicating copy to clipboard operation
LibAFL copied to clipboard

Find a mechanism to enforce Metadata dependencies

Open andreafioraldi opened this issue 4 years ago • 1 comments

At the current state, we don't have any mechanism to enforce the presence of some testcase or state metadata apart from returning errors at runtime when one component that needs such metadata want to use it without success.

Can we enforce this earlier in the code, e.g. when the component is created? Or even at compile time maybe?

andreafioraldi avatar Mar 05 '21 13:03 andreafioraldi

the presence of a testcase could be done at compile time perhaps with include_bytes!("../corpus/testcase1") but then compile-time and runtime could potentially diverge if that file changes or disappears

evanrichter avatar Jan 01 '22 21:01 evanrichter

Feedbackstate has been refactored so this isn't really needed anymore, I think. Closing

domenukk avatar Jan 26 '23 01:01 domenukk