You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default ld_preload_fuzz reads host_config.bitmap_size from the configuration and maps a memory area with the corresponding size, then it overwrites agent_config.coverage_bitmap_size when processing an LTO-compiled binary but doesn't reallocate the memory.
There is no such argument about bitmap_size when generating configuration using nyx_config_gen.py, so the value will come from the included default_config_kernel.ron, which is 0x10000.
This works well in most cases but may crash when the map_size of the binary is larger than 0x10000. It would be great to reallocate the memory after detecting the map_size, or just add an argument to the config generator for customizing the map_size.
The text was updated successfully, but these errors were encountered:
By default
ld_preload_fuzz
readshost_config.bitmap_size
from the configuration and maps a memory area with the corresponding size, then it overwritesagent_config.coverage_bitmap_size
when processing an LTO-compiled binary but doesn't reallocate the memory.There is no such argument about
bitmap_size
when generating configuration usingnyx_config_gen.py
, so the value will come from the includeddefault_config_kernel.ron
, which is 0x10000.This works well in most cases but may crash when the
map_size
of the binary is larger than 0x10000. It would be great to reallocate the memory after detecting themap_size
, or just add an argument to the config generator for customizing themap_size
.The text was updated successfully, but these errors were encountered: