Skip to content

Libafl_libfuzzer: Timestamps are not preserved across crashes/timeouts #1455

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

Closed
domenukk opened this issue Aug 24, 2023 · 4 comments
Closed
Assignees
Labels
bug Something isn't working libafl_libfuzzer Bugs or features relating to libafl_libfuzzer

Comments

@domenukk
Copy link
Member

If you launch the manager everytime, then the timestamp is not preserved across restarts

Originally posted by @tokatoka in #981 (comment)

@domenukk domenukk added the bug Something isn't working label Aug 24, 2023
@tokatoka
Copy link
Member

I think this happens also in non-libafl_libfuzzer fuzzer

@tokatoka tokatoka added the libafl_libfuzzer Bugs or features relating to libafl_libfuzzer label Sep 24, 2023
@tokatoka
Copy link
Member

tokatoka commented Sep 25, 2023

without afl_exec_sec then execs/sec is broken.
because when the restart happens the last_window_time is updated here
https://github.com/AFLplusplus/LibAFL/blob/main/libafl/src/monitors/mod.rs#L285

but the executions count adds the executions count even before the restart.
so the time is counter after the restart. but the execution count is from the very start of the fuzzing

@addisoncrump
Copy link
Collaborator

Do we just add that feature and it's fixed? 😅

@tokatoka
Copy link
Member

yes. but there's still something that I don't understand with this bug. I'll debug it tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working libafl_libfuzzer Bugs or features relating to libafl_libfuzzer
Projects
None yet
Development

No branches or pull requests

3 participants