From 36d7f642e71207d04f5da80530da552e06447337 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 10 Nov 2026 12:37:33 -0300 Subject: syscalls: what writev's buffers hold is captured, by the debugger and the agent musl's printf and Zig programs write through writev: pardes drawing an image showed nothing of the kitty graphics commands it sends until this. The README says what Lua and pardes were run with and what they showed. --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index ce44bf4..8e2766b 100644 --- a/README.md +++ b/README.md @@ -104,6 +104,22 @@ everything instrumented (lines, calls, variables, stores, in all of its A moment a C line of an interpreter is a great many moments: choose what is instrumented (`--only`, `--mem`, `--instr`) before choosing to wait. +The other backends on the same Lua, uninstrumented: the agent's +allocations and syscalls (368 allocations, no ptrace), breakpoints on +`luaH_resize` (48 hits), source lines from DWARF (53 000 a second), +counters and page faults from perf (10.8 million instructions, 89 faults). + +And pardes drawing an image, through its own harness (`zig build +image-harness` there, the command it runs given to `ztrace run --preload +... --syscalls --capture 2048`): the harness and the pardes it starts are +one recording, 9 threads, and the kitty graphics protocol is there to read +in the captured writes: pardes asks (`_Gi=1,a=q`), the terminal answers +(`_Gi=1;OK`), pardes sends the pixels (`_Gf=32,s=2,v=2,i=1;DU3n/w...`). Two +limits it shows: a recording's state is one address space, so a child's +memory and mappings share its parent's maps (its events are told apart by +thread); and pardes allocates through its own heaps, so `--alloc` sees only +what its C libraries ask of libc. + ## Together The backends are not modes to choose between: they feed one sink. A -- cgit v1.3