Skip to content
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

Split edges_map_size and edges_map_size_alloc #2012

Merged
merged 14 commits into from
Apr 17, 2024
Merged

Split edges_map_size and edges_map_size_alloc #2012

merged 14 commits into from
Apr 17, 2024

Conversation

tokatoka
Copy link
Member

@tokatoka tokatoka commented Apr 6, 2024

No description provided.

@tokatoka
Copy link
Member Author

tokatoka commented Apr 6, 2024

The purpose of this pr is to

  1. Avoid using edges_map_size = 2mb for most fuzzers.
  2. yet allocate 2mb for the map
    This way we can grow the size later as it wants when the fuzzer starts the initialization

@domenukk
Copy link
Member

domenukk commented Apr 8, 2024

Something like EDGES_MAP_SIZE and EDGES_MAP_SIZE_MAX?

@tokatoka tokatoka merged commit c50af44 into main Apr 17, 2024
76 of 78 checks passed
@tokatoka tokatoka deleted the edges_map-size branch April 17, 2024 15:58
mkravchik added a commit to mkravchik/LibAFL that referenced this pull request Apr 18, 2024
addisoncrump pushed a commit that referenced this pull request Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants