Home /Modules/debugger/README.md

README.md

debugger/README.md · 44 line(s) · markdown

<img align="right" src="https://github.com/mearvk/SLeeLa/blob/master/images/debian/debian-logo.png" width="75" height="75" alt="SLeeLa">

<img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-logo-004.jpg" alt="SLeeLa">

SLeeLa Debugger

The SLeeLa Debugger is a development-time diagnostic layer for the SLeeLa software lifecycle.

Build -> Launch -> Break -> Inspect -> Trace -> Diagnose -> Test -> Reproduce -> Report

It provides a portable core for breakpoints, watchpoints, source locations, stack frames, runtime events, assertions, exceptions, test correlation, coverage correlation, sanitizer correlation, regression correlation, and deterministic reports.

It is backend-neutral. Future process adapters may use ptrace, Mach task APIs, Windows debugging APIs, LLDB, or another supported facility.

Build: make -C debugger

Run: ./debugger/sleela-debugger --self-test ./debugger/sleela-debugger --report debugger/example-report.txt

The debugger records and analyzes events; it does not execute arbitrary payloads or bypass authorization.

Corrections

Fixed build-blocking defects: debugger_backend.hpp defined RegisterSnapshot and its backend virtual methods twice, and that RegisterSnapshot also clashed with a different struct of the same name in debug_engine.hpp. The duplicates were removed and the backend view renamed to BackendRegisterSnapshot; a missing <memory> include (for std::unique_ptr) and a literal-\n corruption were also fixed. The debugger now builds. See the 2026-10-03 entry in ../REVISIONS.md.


SLeeLa

<p align="center"><img src="images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>