Fix counting stage execs for user inserts

[baryluk]

Pretty obvious, because of the number of iterations of the outer loop few lines later:

for (i = 0; i <= len; i++) {

Without the fix the progress can (and does for me) go over 100% otherwise.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[baryluk]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[baryluk]

No. It would make it inconsistent with rest of the afl code.

…

On Tue, 4 Aug 2020, 02:15 Max Moroz, ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In afl-fuzz.c <#73 (comment)>: > @@ -5980,7 +5980,7 @@ static u8 fuzz_one(char** argv) { stage_name = "user extras (insert)"; stage_short = "ext_UI"; stage_cur = 0; - stage_max = extras_cnt * len; + stage_max = extras_cnt * (len + 1); would it be better to fix the loop condition instead (line 5989) ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#73 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA254SZ467QBGR4YP4BKXDR65HKTANCNFSM4KSYVS5A> .

[Dor1s]

Thanks @lszekeres for taking a look and sorry @baryluk for the confusion from my end.