Open RCasatta opened 2 years ago
In https://github.com/rust-bitcoin/rust-bitcoin/ we have some potential issues on 32 bits architectures because usize is obviously different on this architecture.
usize
Since 32 bits software could run on 64 bits machine, I would have liked fuzzing with a target different than the host machine, like i686-unknown-linux-gnu but I have seen is not possible to specify a different triplet than the host system with cargo hfuzz https://github.com/rust-fuzz/honggfuzz-rs/blob/f45aef1b59736fcfc215eca09aca42e49bbf36db/src/bin/cargo-hfuzz.rs#L23
i686-unknown-linux-gnu
cargo hfuzz
I would like to know if this is some issue only of how parameters are handled in cargo hfuzz or if there are inherently other issues in the fuzzing process on 32 bits (on a 64 bits host)
In https://github.com/rust-bitcoin/rust-bitcoin/ we have some potential issues on 32 bits architectures because
usizeis obviously different on this architecture.Since 32 bits software could run on 64 bits machine, I would have liked fuzzing with a target different than the host machine, like
i686-unknown-linux-gnubut I have seen is not possible to specify a different triplet than the host system withcargo hfuzzhttps://github.com/rust-fuzz/honggfuzz-rs/blob/f45aef1b59736fcfc215eca09aca42e49bbf36db/src/bin/cargo-hfuzz.rs#L23I would like to know if this is some issue only of how parameters are handled in
cargo hfuzzor if there are inherently other issues in the fuzzing process on 32 bits (on a 64 bits host)