-
Notifications
You must be signed in to change notification settings - Fork 533
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Target function #393
Comments
That is because WinAFL uses persistent mode, meaning it does not restart the target process between iterations. WinAFL uses dynamic binary instrumentation to get coverage. Instrumenting the process initially is expensive, however that is the price you only have to pay once per process. That's why, instead of restarting the process for every iteration, WinAFL runs the user-specified target function in a loop. In order for that to work, the target function must behave in a relatively standalone way and have the requirements you mentioned. |
Thank you very much
842294334
***@***.***
…------------------ 原始邮件 ------------------
发件人: "Ivan ***@***.***>;
发送时间: 2022年11月1日(星期二) 下午5:30
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [googleprojectzero/winafl] Target function (Issue #393)
That is because WinAFL uses persistent mode, meaning it does not restart the target process between iterations. WinAFL uses dynamic binary instrumentation to get coverage. Instrumenting the process initially is expensive, however that is the price you only have to pay once per process. That's why, instead of restarting the process for every iteration, WinAFL runs the user-specified target function in a loop. In order for that to work, the target function must behave in a relatively standalone way and have the requirements you mentioned.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Why does winafl target function have to finish opening and closing testcase(files) when afl does not have to manually specify object functions?
The text was updated successfully, but these errors were encountered: