I've built LEAX (Leak Analyzer & eXplorer), a CLI tool for analyzing memory leaks in C programs.

It orchestrates:

* Valgrind for leak detection * GDB for reconstructing allocation and execution context * A structured analysis layer to trace the allocation lifecycle * An AI component that explains the root cause and proposes targeted fixes

Leak detection and memory tracing are fully deterministic and based on parsed Valgrind and GDB data. The AI layer does not guess the leak — it interprets the reconstructed execution path to explain what happened to the pointer during the program's lifetime and suggest how to resolve it.

The goal is to turn raw “definitely lost” reports into a clear, causal story with actionable guidance.

LEAX is still actively evolving, and I’m continuously refining the tracing and explanation pipeline. I’m very open to feedback, suggestions, and architectural criticism.

Happy to answer technical questions about the analysis or tracing approach.