From 66a2a7cf733f6abc1f79561c52d901ce67019fb1 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 10 Nov 2026 16:03:43 -0300 Subject: trace: what the context draws is in the recording; SQLite on the ladder An instruction's string carries its source line and, for a direct call, how many parameters the callee takes (DWARF); telescope.frames gives each frame's extent on the stack; with --alloc the debugger watches each live allocation and the allocator's header before it, changes only, 256 KiB a stop at most. C++ names are shown and found as the source has them (the command links the C++ runtime for its demangler). SQLite 3.50.4 through every backend, measured (README, bench/sqlite.sh). It found two faults: a file compiled by its full path was recorded under a path joined onto the compile directory, and ztrace run noticed a target's exit up to 10 ms late. Co-Authored-By: Claude Fable 5.2 --- build/debugger.zig | 2 ++ 1 file changed, 2 insertions(+) (limited to 'build/debugger.zig') diff --git a/build/debugger.zig b/build/debugger.zig index a2611b2..9779ecd 100644 --- a/build/debugger.zig +++ b/build/debugger.zig @@ -89,6 +89,8 @@ pub fn add(ctx: Ctx) void { show.addFileArg(recording); show.expectStdOutMatch(" 89 breakpoint\n"); step.dependOn(&show.step); + // ... which the library's tests read too. + paths.addOptionPath("fib_recording", recording); // A source line a moment, a watched global, to the exit code. const lines = b.addRunArtifact(ctx.exe); -- cgit v1.3