From aefde257db6e7cf683b923498c0d471885ab67a9 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Thu, 12 Nov 2026 01:40:04 -0300 Subject: record: --until ends the recording at a place The ASan scene cut its run by a count of steps, which moves with the compiler; --until __asan_report_store1 ends it where the report begins. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_016Y9MNCKgYCGiANnEwcEQxa --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 71142c3..7b8fcfe 100644 --- a/README.md +++ b/README.md @@ -518,7 +518,9 @@ 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. How much of the context a stop keeps is +start before the first stop, and `--until WHERE` ends the recording at +the first stop there (`--until __asan_report_store1` stops an ASan run +where its report begins, before the million instructions of writing it). 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 -- cgit v1.3