From 36bb1c332a124cb4d437dd8386b267ee58310a5d Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 10 Nov 2026 22:02:01 -0300 Subject: record: how much of the context a stop keeps is asked for --around BYTES of memory each side of what a pointer leads to, for a viewer that shows the region and not the word; --disasm ROWS above and below the pc; and every word of the --stack bytes is followed as a pointer, not the first sixteen. Co-Authored-By: Claude Fable 5.2 --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 1dd2b84..4d7a0ae 100644 --- a/README.md +++ b/README.md @@ -320,7 +320,14 @@ breakpoint 1 at 563f798b1814 fib+4 (fib.c:4) `ztrace record` is the same debugger left to run: `--by insn|line|syscall|break` says where it stops, `-b` adds breakpoints, `-w` watches, `--strace` prints the syscalls, `--from main` runs through the loader and the C library's -start before the first stop. In a program, it is `zt.Debugger`: +start before the first stop. How much of the context a stop keeps is +asked for: `--stack BYTES` above the stack pointer (128), every word of +it followed as a pointer; `--around BYTES` of memory each side of what a +pointer leads to (0: the 32 bytes at it); `--disasm ROWS` of instructions +above and below the pc (8). On the list of `anim/tools` by instruction, +`--stack 512 --around 64 --disasm 24` is 184 bytes a moment against 159, +and 27 000 moments a second against 45 000. In a program, it is +`zt.Debugger`: ```zig var d = try zt.Debugger.spawn(gpa, io, path, argv, envp, recorder.sink()); -- cgit v1.3