[test] add fuzz_tbor_part_info

[David Zimmermann (zimmy87)]

No description provided.

[Copilot]

Pull request overview

Adds a new libFuzzer target to exercise the TBOR PartInfo operation in the fuzzing crate, integrating it into the fuzz workspace binaries.

Changes:

• Added fuzz_tbor_part_info fuzz target under fuzz_targets/ddi/tbor/.
• Registered the new fuzz target as a [[bin]] in fuzz/Cargo.toml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
fuzz/fuzz_targets/ddi/tbor/fuzz_tbor_part_info.rs	New fuzz harness invoking the TBOR PartInfo request against the emulator device.
fuzz/Cargo.toml	Adds the fuzz_tbor_part_info binary entry so it can be built/run by the fuzz crate tooling.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Suppressed comments (1)

fuzz/fuzz_targets/ddi/tbor/fuzz_tbor_part_info.rs:16

• This fuzz target ignores the fuzzer input and always issues the same deterministic PartInfo request, so coverage won’t vary with the corpus and libFuzzer will quickly stop making progress (it becomes a repeated smoke test rather than a fuzz target). Consider using input to exercise a variable code path, e.g. fuzz the TborPartInfoResp type-specific decoder on arbitrary bytes while still optionally keeping the emulator round-trip for the real opcode.

fuzz_target!(|_input: &[u8]| {
    let dev = common::open_emu_dev();
    let req = TborPartInfoReq;
    common::fuzz_exec_op_tbor(&dev, &req);
});