Files
reverse-engineering-anything/docs
David Muñoz Rey 33ecda025f fix(ghidra): name the code seed recovery for addresses outside the listing (#10682)
inspect_native_instruction reports `not-in-listing` when an address lies
in Ghidra's memory but the listing has no instruction or defined data
there. No decode is attempted, so the answer does not show the bytes are
data, yet the result named no way forward. #10623 added the declared-seed
recovery for procedure_not_found and not_in_procedure; this is the
instruction-level sibling, where a `code` seed applies.

A not-in-listing answer now carries ghidraNotInListingLimitation(source).
It names a `code` seed (or a `function` seed for an entry point) in
REA_GHIDRA_SEED_FILE, says which setting to unset first for a selected
project or checkpoint, and does not assert that the address holds code.
decoded, data and other statuses are unchanged. The installation guide's
seed section lists the new carrier.

Validation: src/ghidra/GhidraProvider.behavior.test.ts fails 1/298 with
the caveat removed and passes 298/298 with it; check:fast passes. No
real Ghidra run.

Refs morluto/rea#3767
2026-11-21 20:47:42 +01:00
..

Documentation directory

Find an installation step, investigation guide, or contributor reference by task. The REA website has worked examples and product pages.

Getting started

Desktop applications

Agent environments

Native binaries

JavaScript and Electron

Browser and captured websites

Android applications

Apple applications

.NET assemblies

Firmware

HarmonyOS packages

Packages and metadata

WebAssembly

EVM contracts

Databases and recorded packets

Process capture and instrumentation

Provider setup and formats

Contracts and evidence

Development and verification

Release migrations

Signal recordings

Generated files and release records

Path Owner and update command
public/product-catalog.json Ignored contract projection; npm run docs:generate
verification/managed-conformance-*.json Ignored managed conformance projections; npm run evidence:generate
error-contract.schema.json Tracked schema from contracts; npm run docs:error-schema
user-visible-errors.csv Generated error code and category per domain and provider-owned error case; npm run docs:error-schema
releases/<version>.contributions.json Durable release contribution record; follow the release guide

Regenerate catalogs and Evidence projections from their canonical source. Release records preserve the exact commit messages and references for each release. Guides share authored images in assets/.