Skip to content

docs(qemu): clarify post_exec runs after harness completion#3671

Closed
Tanmay140906 wants to merge 6 commits intoAFLplusplus:mainfrom
Tanmay140906:docs-post-exec-baremetal
Closed

docs(qemu): clarify post_exec runs after harness completion#3671
Tanmay140906 wants to merge 6 commits intoAFLplusplus:mainfrom
Tanmay140906:docs-post-exec-baremetal

Conversation

@Tanmay140906
Copy link
Copy Markdown
Contributor

Description

This PR clarifies the execution timing of EmulatorHooks::post_exec, documenting
that it runs after the harness completes and after snapshot restoration.

It also adds a small lifecycle note in the qemu_baremetal low-level example to
make it explicit that qemu().run() completes the full harness execution cycle.

This resolves the confusion described in #2765 regarding guest memory reads in
post_exec.

Checklist

  • I have run ./scripts/precommit.sh and addressed all comments

@Tanmay140906
Copy link
Copy Markdown
Contributor Author

CI failure appears unrelated to this change.
cargo doc --no-deps passes locally; the failure occurs in the qemu_tmin
runtime test (Fuzzer-respawner, child exited with 0), which is outside the
scope of this PR.

@Tanmay140906
Copy link
Copy Markdown
Contributor Author

@rmalmain , could you please review this PR and guide me for GSoC 2026? I am trying to make contributions to LibAFL for being selected in GSoC and I need some guidance and answers to few of my questions. Could you please help me?

@tokatoka
Copy link
Copy Markdown
Member

there's no guarantee that we are participating in GSoC 2026.

@Tanmay140906
Copy link
Copy Markdown
Contributor Author

Okay

qemu.write_phys_mem(input_addr, buf);

// `qemu().run()` completes the full harness execution cycle.
// The snapshot is restored before this call returns.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not correct I think

@domenukk
Copy link
Copy Markdown
Member

domenukk commented Feb 6, 2026

I don't think we need to really nudge the user to anything here (unless @rmalmain disagrees)

@domenukk domenukk closed this Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants