[GH-ISSUE #16] Fix false-positive paths in real-Hopper verification #21

Closed
opened 2026-10-15 18:20:01 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/16

Problem

The real-Hopper verifier treats the paginated list_procedures response as an address-keyed map. It can therefore pass items rather than a real procedure address to batch_decompile, then accept an embedded per-item error as successful evidence.

Scope

  • Parse the first real procedure address from structured page output.
  • Require non-empty pseudocode for a valid procedure.
  • Exercise analyze_function, callers, callees, and xrefs against known real binaries.
  • Reject success-shaped results containing per-item errors.
  • Validate target switching and clean shutdown without weakening existing assertions.

Acceptance criteria

  • The verifier fails when decompilation receives an invalid address.
  • The verifier fails on empty or error-only pseudocode.
  • At least two distinct real binaries pass the complete workflow.
  • Assertions validate semantic result content, not merely object shape or key count.
Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/16 ## Problem The real-Hopper verifier treats the paginated `list_procedures` response as an address-keyed map. It can therefore pass `items` rather than a real procedure address to `batch_decompile`, then accept an embedded per-item error as successful evidence. ## Scope - Parse the first real procedure address from structured page output. - Require non-empty pseudocode for a valid procedure. - Exercise `analyze_function`, callers, callees, and xrefs against known real binaries. - Reject success-shaped results containing per-item errors. - Validate target switching and clean shutdown without weakening existing assertions. ## Acceptance criteria - The verifier fails when decompilation receives an invalid address. - The verifier fails on empty or error-only pseudocode. - At least two distinct real binaries pass the complete workflow. - Assertions validate semantic result content, not merely object shape or key count.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#21
No description provided.