Files
reverse-engineering-anything/scripts
Muhammad Hamzaandmorluto 93c8e0c0c8 fix(erlang): disclose BEAM bytes trailing the declared FOR1 form (#9673)
* fix(erlang): disclose BEAM bytes trailing the declared FOR1 form

A conformant FOR1 container sizes its form to the whole file, so bytes
past the form end are an unexamined appended or corrupt region. The
inspector decoded chunks only within the form but still reported
coverage.status "complete" with no mention of the surplus, so a caller
could not distinguish a clean BEAM from one carrying foreign trailing
bytes.

Compute the trailing byte count, report coverage.status "partial" with a
trailing_bytes field, and append a limitation naming the form end and the
unexamined count. Clean containers stay "complete" with trailing_bytes 0.

* fix(erlang): reparse retained BEAM Evidence without the trailing-bytes field

Evidence retained by a build predating coverage.trailing_bytes has no such
property, and projectErlangBeamView reparses that record with the strict
erlangBeamSchema. A required field rejected those records with an input error
before any summary or page could render, breaking the offline retained-Evidence
flow even for clean files.

Default coverage.trailing_bytes to 0 so historical records reparse while every
new parse still emits the concrete count and preserves each record's stored
status.

* fix(erlang): keep retained BEAM trailing coverage unknown, not zero

Defaulting coverage.trailing_bytes to 0 manufactured a "no trailer" reading for
Evidence retained before the field existed, even when its retained bounds
(artifact.bytes versus form.location.bytes) prove a trailer. Make the field
optional so a pre-field record reparses as unknown instead of a fabricated
zero, while every new parse still emits the concrete count.

* fix(erlang): admit chunk extents before applying count limits

* docs(erlang): explain trailing BEAM coverage

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 07:44:30 +00:00
..