Home /Modules/decompiler/FORMATS.md

FORMATS.md

decompiler/docs/FORMATS.md · 43 line(s) · markdown

Slecompiler™ Formats and Native Artifact Classes

Max Rupplin - MEARVK LLC - 2026

Slecompiler™ treats container format and software role as separate concepts. An ELF file can be an executable, shared library, relocatable object, or kernel module; the parser therefore records both the container and detected artifact class.

ContainerNative classesTypical Linux examples
ELF32/ELF64Executable, DynamicLibrary, RelocatableObject, KernelModule/bin/, /lib/lib*.so*, .o, .ko
GNU arStaticArchivelibSomething.a
PE/COFFExecutable, DynamicLibrary, Driver, RelocatableObject.exe, .dll, .sys, .obj
Mach-OExecutable, DynamicLibrarymacOS binaries and dylibs
RawRawArtifactfirmware, dumps, unknown blobs
WebAssemblyPlanned VM/IR adapter.wasm

ELF shared libraries

Slecompiler™ should preserve SONAME and filename; DT_NEEDED dependencies; dynamic and regular symbol tables; symbol version definitions and requirements; PLT/GOT-related relocation evidence; TLS sections and relocations; init/fini arrays; GNU build ID and note records; GNU hash and SysV hash tables; and section/program-header permissions and load ranges.

Linux .ko kernel modules

A .ko is normally an ELF relocatable kernel module. Slecompiler™ should inspect, when present:

Analysis remains static. A .ko is never inserted into a running kernel by Slecompiler™.

Archives and object files

For .a archives, the archive is modeled as a container of members. Each member can be analyzed as an ELF/COFF relocatable object while retaining archive/member provenance. .o files are analyzed directly as relocatable objects, including symbols and relocation sites.

All parsers must validate bounds before reading a header, table, string, section, segment, relocation, or symbol. Malformed input is reported as an analysis error rather than executed.