Machine State

SmallWorld provides its own representation for machine state, which is used to initialize an emulation or analysis attempt, as well as to retrieve results from an emulator once execution is complete. This provides two key benefits:

1. The machine state representation is not tied to a particular emulator or analytic back-end. This makes it very easy to repurpose a single harness, as well as any pre-processing or post-processing code for multiple experiments.

2. Machine state can be transferred between emulators, as long as they meet SmallWorld’s Emulators interface

• Values in Smallworld
  • Contents
  • Labels
  • Data Types
  • Implementations
• The Machine Object
  • Adding State to a Machine
  • Applying and Extracting a Machine
  • Accessing Extracted State
  • Execution Helpers
  • Exit Points
  • Bounds
  • Constraints
• The CPU Object
  • Registers
  • Register Aliases
  • Fixed Registers
• Memory Objects
  • Values in Memory
  • Implementations
    • Unstructured Memory
    • Execution Stacks
    • Heaps
    • Executables
    • Object File Loaders
      • Platform Verification
      • Load Address
      • Memory Layout
      • Entry Point
      • Bounds
      • Linking and Loading
        • PE32+ Relocations
        • PE32+ Imports and Exports
        • ELF Symbols and Relocations
      • Core Dump Loader
• Event Handlers
  • Instruction Hooks
  • Function Models
  • MMIO Models
• C Library Models
  • ABI Support
  • Function Support by Header