This commit updates how the NormalMemoryConfig works during fuzzing. Previously this was either 0 or an arbitrary 32-bit number. This ended up not not handling cases such as 4GiB exactly which is 1 larger than the 32-bit range. Additionally 33+-bit numbers were never tested. This intends to expand our fuzz coverage here by most of the time using the default settings of Config and then otherwise selecting amongst an "interesting" set of numbers such as 0, powers of two, etc.
This commit updates how the
NormalMemoryConfigworks during fuzzing. Previously this was either 0 or an arbitrary 32-bit number. This ended up not not handling cases such as 4GiB exactly which is 1 larger than the 32-bit range. Additionally 33+-bit numbers were never tested. This intends to expand our fuzz coverage here by most of the time using the default settings ofConfigand then otherwise selecting amongst an "interesting" set of numbers such as 0, powers of two, etc.