FILE → VIRTUAL ADDRESS / INSPECTION ONLY
The container.
Then your bits.
Bitborn adds 64 ELF header bytes and one 56-byte load header around its literal Linux programs. Select a field to see the bytes that tell the loader where execution begins.
No imported program is executed. ELF64, little-endian, x86-64, ET_EXEC/ET_DYN; at most 1 MiB and 128 program headers.
Loading reviewed files…
DECLARED ENTRY MAPPING
Where do the bytes begin?
—
Header fields
Select a field. These values describe the file; they do not generate instructions.
Actual file bytes
Select a field or byte.
Arrow keys move between bytes; Home/End select the first/last visible byte.
—
File → memory segments
PT_LOAD maps file bytes; a larger memory extent has zero-filled trailing bytes. No virtual memory is allocated by this viewer. Other segment types are listed without resolving their contents.
Packaging is not an assembler.
The reviewed ELF examples use a single RX load segment. The entry address is 0x400078: virtual base 0x400000 plus file offset 120. The bytes after those headers come unchanged from their .bits sources. Linux x86-64 CI executes the curated examples; this page only inspects files.
Passing these structural checks is not proof that a loader accepts a file, that its code is safe, or that it runs correctly. Section contents, relocations, interpreter resolution and execution are outside this viewer; extended table numbering is rejected. ET_DYN addresses need a runtime load bias.