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
Increasing the bitmap size in configuration file config.ron leads to a crash:
[2024-10-12] 16:53:37 Starting Fuzzing...
thread 'fuzzer_1' panicked at fuzzer/src/fuzzer.rs:344:17:
index out of bounds: the len is 65536 but the index is 65536
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at fuzzer/src/main.rs:489:44:
RAND_2698731594: Any { .. }
After some debugging it turns out that the value 65536 is hardcoded within Nautilus:
return (shm_id, trace_bits as *mut [u8; 1 << 16]);
The array size is fixed here, and is not set by configurations. The mismatch between the hardcoded value 1 << 16 and the expected value from config.ron leads to the error.
The text was updated successfully, but these errors were encountered:
Hi,
Increasing the bitmap size in configuration file
config.ron
leads to a crash:After some debugging it turns out that the value
65536
is hardcoded within Nautilus:The array size is fixed here, and is not set by configurations. The mismatch between the hardcoded value
1 << 16
and the expected value fromconfig.ron
leads to the error.The text was updated successfully, but these errors were encountered: