summaryrefslogtreecommitdiff
path: root/src/trace/syscalls.zig
Commit message (Collapse)AuthorAge
* syscalls: an argument's name, by callGabriel Schneider7 days
| | | | | names(nr) gives fd, buf, count for read and its like: what a viewer of a syscall labels an argument with, where it had only the argument's kind.
* syscalls: what writev's buffers hold is captured, by the debugger and the agentGabriel Schneider7 days
| | | | | | 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.
* debugger: steps by instruction and line, breakpoints, hooks, watches, ↵Gabriel Schneider7 days
threads; ztrace dbg ptrace.zig follows the threads a target makes, attaches, tells a step from a breakpoint, and writes memory in one call (through /proc/pid/mem where the page is read-only). Debugger.zig is the layer above: cont, stepi, step (a source line, through std.debug's DWARF), breakpoints with hooks, syscall stops and hooks with the path or buffer captured, watched regions sent as the words that changed, and every stop an event. Symbols.zig is modules, ELF symbols and line tables; syscalls.zig their names and shapes. ztrace dbg is a small REPL on it that records as it goes and looks back into the recording; ztrace record stops by instruction, line, syscall or breakpoint, prints syscalls as strace does, and ends cleanly when the recording is full. Co-Authored-By: Claude Fable 5.2 <[email protected]>