Topics

UTTORI ASM ยท IN DEVELOPMENT

Replay debugging

Inspect recorded execution with source mapping without a running emulator.

Assembly: Build Binary now always emits an identity-matched pair: the configured ROM output and <output>.debug.json. The build result includes the binary SHA-256, debug-map fingerprint, target, architecture, and per-artifact change state. Unsaved editor buffers are fingerprinted from the exact overlay bytes used by the assembler.

You can also build an exact binary and debug map from the CLI:

uttori-asm main.asm build/rebuilt-content.sfc --debug

Then choose Uttori ASM: Replay Debug or add this launch configuration:

{
  "type": "uttori-asm",
  "request": "launch",
  "name": "Debug Uttori ASM (Replay)",
  "backend": "replay",
  "program": "${workspaceFolder}/build/rebuilt-content.sfc",
  "debugMap": "${workspaceFolder}/build/rebuilt-content.sfc.debug.json",
  "sourceRoot": "${workspaceFolder}"
}

The extension rejects stale maps whose binary identity does not match. Without a replay path it synthesizes a deterministic timeline from the mapped source ranges. Optionally set replay to a versioned snapshot JSON file when testing a specific execution trace. The adapter runs inline in the extension host and has no emulator dependency.