Skip to content

Fuzz testing on 32 bits #60

Open
Open
@RCasatta

Description

@RCasatta

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.

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

fn target_triple() -> String {

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions