Overview

This crate contains precompiled .sla and .pspec configuration files for use with libsla or other crates that interface with Ghidra SLEIGH. The configuration files are sourced from Ghidra version 11.4.

Example

Specify the processor(s) you wish to use via feature flags.

sleigh-config = { version = "1", features = ["x86"] }

Then use a crate such as libsla that uses these configuration files to interface with Ghidra SLEIGH:

let sleigh = libsla::GhidraSleigh::builder()
    .processor_spec(sleigh_config::processor_x86::PSPEC_X86_64)?
    .build(sleigh_config::processor_x86::SLA_X86_64)?;

The configurations available for the x86 processor are:

sleigh_config::processor_x86::SLA_X86;
sleigh_config::processor_x86::SLA_X86_64;
sleigh_config::processor_x86::PSPEC_X86;
sleigh_config::processor_x86::PSPEC_X86_16;
sleigh_config::processor_x86::PSPEC_X86_16_REAL;
sleigh_config::processor_x86::PSPEC_X86_64;
sleigh_config::processor_x86::PSPEC_X86_64_COMPAT32;

Processors

The following are the list of processor configurations available in Ghidra.

• 6502
• 68000
• 8048
• 8051
• 8085
• AARCH64
• ARM
• Atmel
• BPF
• CP1600
• CR16
• DATA
• Dalvik
• HCS08
• HCS12
• JVM
• Loongarch
• M16C
• M8C
• MC6800
• MCS96
• MIPS
• PA-RISC
• PIC
• PowerPC
• RISCV
• Sparc
• SuperH
• SuperH4
• TI_MSP430
• Toy
• V850
• Xtensa
• Z80
• eBPF
• tricore
• x86

FAQ

Why are the SLA configuration files not XML?

In Ghidra 11.1 the SLA configuration file format was changed to a binary format.

Is there a way to discover configurations programmatically?

Yes. The global SLA_DATA and PSPEC_DATA arrays can be used to iterate over all configurations.