Formats and processors
Processors
Section titled “Processors”Basilisk does not rewrite Ghidra’s processor descriptions. It reads Ghidra’s language files unchanged:
the SLEIGH specifications (.slaspec, .sinc) that describe each instruction set, and the language
definitions (.ldefs), processor specifications (.pspec), compiler specifications (.cspec) and loader
opinions (.opinion) around them.
The list of modules and how to name a language is on Processors.
Binary formats
Section titled “Binary formats”| Format | Today | Planned |
|---|---|---|
| ELF | Parser | Loader and relocations (M4) |
| PE, Mach-O | — | Parsers and loaders (M4) |
| Raw binary, Intel hex | — | Loaders (M4) |
| COFF, OMF, NE, MZ, PEF, SOM, XCOFF, a.out | — | M4–M10 |
| DWARF, PDB | — | M6 |
The ELF parser
Section titled “The ELF parser”The parser reads everything Ghidra’s ELF loader uses: headers, sections and segments, symbol tables, relocations, dynamic information, notes and version tables, for 32-bit and 64-bit files in either byte order. It is tolerant in the way Ghidra’s is: a damaged table is reported and the rest of the file is still read.
Hostile input
Section titled “Hostile input”Programs that are reverse-engineered are often built to break tools. Every parser of untrusted input in Basilisk is fuzzed, and none may panic, overflow or allocate without bound on a malformed file; a bad file gives an error, not a crash. See how results are checked.