| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | event: what instrumentation puts in call, ret, line, variable, mem_write | Gabriel Schneider | 7 days |
| | | | | | | | | | | Comments only: call's callee is a name's string id when the backend has names, a3 its type; ret's aux is the size of the value; a variable's aux its parameter number; a pc may be 0; a mem_write may hold the first bytes of a large write. Co-Authored-By: Claude Fable 5.2 <[email protected]> | ||
| * | recorder: moments in batches, and the heap, the stack, variables, lines and ↵ | Gabriel Schneider | 7 days |
| | | | | | | | | | | | | | | | | mappings in each A transaction a moment cost 10 µs and 1 KB before the moment's own data: the list's path copied each time. Moments now gather 256 to a transaction, each frozen by its own cursor so the list grows in place, and a thread's fields sit in the moment's map instead of two maps down: a small moment is 284 bytes and 1 µs, an instruction step with registers 780 bytes. A moment also folds alloc/free into the live heap, call/ret into each thread's stack, variable into the live variables (a local leaves with its call), line, and map/unmap, so a viewer reads any of them at any moment without replaying. | ||
| * | ztrace: the event, the ring, the recording, a ptrace loop | Gabriel Schneider | 7 days |
| One 64-byte Event for every backend; a shared-memory ring from target to tracer with stop/resume; a Recorder that folds events into xitdb moments (registers, memory in 64-byte chunks with known-byte masks, strings) and a Trace that reads any moment back; a minimal ptrace Process; ztrace record, run and dump. Per-area build files so the areas grow apart. | |||
