| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the heap as a scene
From the user. Direction and nearness are rules: the idea, the source,
its instructions, the callee and the kernel go down the frame, a call
goes down and a return comes up, and every tie runs one of those ways.
The disassembly can descend: a window a call depth, the caller keeping
three rows with its call waiting, a PLT stub its jump, the kernel at the
bottom on vellum, with verbs descend, cross and ascend. The kernel leaves
the band, which keeps the calls so far as strace writes them; the
backtrace has its newest frame at the bottom. Size words are dropped
from operands and a width is shown as byte cells where nothing else says
it; a compare shows its values and flags, a jump the flags it reads, an
indirect call its target and the slot it was read from. libc's heap is a
scene of blocks that exist (a dump by fields with a size and a protected
pointer read, arcs as the free list, a loupe into the tcache, the list
drawn over malloc's own), storyboarded on glibc 2.44. Mocks 16 to 18.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNCKgYCGiANnEwcEQxa
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
From the user, on the loupe's mock: a pointer in memory named a row two
above it and nothing showed it. In a dump, a loupe and the stack a
pointer whose target is a row of the same panel is an arc in a lane at
the panel's edge, as a jump is in the disassembly: quiet while it stands,
full ink in the step that writes or reads it, a stub when the target is
just off the window. A chain shares a lane. A loupe carries the arcs
among its own rows; the stack's frame chain gets one only when touched.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNCKgYCGiANnEwcEQxa
|
| |
|
|
|
| |
Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNCKgYCGiANnEwcEQxa
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the user, on the 4K mocks: the space was not well used, and the
dense view is better as where a scene starts or as a minimap than as the
frame it works in. The map is the same moment with every panel at full
length on 3840 by 2160, packed by content. The working frame is the 1920
stage again, each panel a window on its column of the map, with the map
at a twentieth in the caption band: windows outlined, marks no window
shows flashing there. dive and surface carry a scene between the two,
each window travelling to its panel's place. The loupe hangs from its
pointer in the working frame. Mocks 16 to 18 are withdrawn; 19 is the
map, 20 the dive in four instants, 21 a loupe with the minimap.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNCKgYCGiANnEwcEQxa
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the user, after the second videos. The stage is 3840 by 2160 at the
same type size: four columns (source, disassembly, state, stack), 69
lines, rows and slots with no lens, 43 with a lens as subject, dumps of
32 rows. Code reads at 1440p and up; the caption, the clock and a lens's
drawing are doubled, and the camera at x2 is the old frame. The stack's
rows carry their offset from rsp and a role. A loupe is the telescope as
a floating panel: the memory round what a pointer leads to, lifted over
the context, a pointer inside it opening the next. The current row is a
white wash, a strike a softened vermilion, held a turned corner; sheet 15
sets the alternatives side by side.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SQLite scene needed blocks the catalogue had no name for; each is
placed. A dump is read by its type or by fields a scene gives it, rows
without one folding into a row that counts them; bytes that are no field
are loose; what a stop did not read is unread and what the kernel took is
given. Addresses and line numbers are as wide as the program needs. The
backtrace can be a lens's drawing, and a lens can change in place. A
continue is a verb of its own: registers strike in a wave, far windows
fade through and arrive without marks, frames two stops share slide. The
kernel's answer is filled before it travels. The calls tree has sizes
past ten leaves and folds past thirteen. Mocks 13 and 14 are two stops of
the SQLite recording.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An independent review of the first videos, frame by frame, is placed in
the catalogue. A lens is a drawing over the program column and its view
over the state column (the dump; the backtrace for calls), which leaves
the stack six slots as subject: the frame whole, from rsp to past rbp.
Operands are whole. A mark covers the bytes that changed. A pin travels
and keeps its side. A call's node is a projection of its return address.
Fast passes are veiled. Captions have numbers a scene can be checked by,
and a scene's first step comes by four seconds. Effects before causes
and panels from different moments are forbidden by name. Mock 12 draws
fib(4) calling fib(2) from the recording.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The README is now the catalogue: atoms, rows, panels, ties, the frame and
the verbs, each block specified once under the name the code uses, with
rules of composition and what is forbidden. From the user's notes on the
context mocks: a lens is a band across the top, its drawing on the left
and the bytes it is drawn from on the right, a hexdump with each field's
bytes marked and read at the row's end; the disassembly is seventeen rows
in address order with a source-line column and an annotation for what
each row read, set or jumped to; a register is pinned to the node it
points at by name; hex is unbroken; and four kinds of tie say which pane
is a view of which (thread, link, projection, echo).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The user's premise: show what pwndbg shows, hide nothing; the semantic
views stay as a lens on the machine. So every frame holds the registers
(all, each followed as a pointer), the stack telescope and the backtrace
in a column that never changes, and the source, the disassembly and the
scene's lens in the other. A value's ink says where it points (stack,
heap, code, data; rwx underlined), its paper says what happened to it.
JetBrains Mono NL for everything mono; the floor is mono 20, which a
phone does not read: what narration depends on is also in the caption.
Mocks 9 to 11 are drawn from a real recording of targets/list.
|
| |
|
|
|
|
|
|
|
|
| |
motion.md: the animation principles as they apply here, a timing chart at
60 fps for each kind of event, revised motion tokens, and a timestamped
critique of the five scenes as first rendered. motion/motion.py draws a
per-panel timing chart of a video and tiles its frames into contact
sheets; charts/ and sheets/ are what the critique was read from. Measured:
in fib 75 steps start three or more panels on the same frame, 68 changes
have no frame in between, and the run is 68 evenly spaced steps.
|
|
|
Lapis page and vellum ink; a role is a form as well as a colour (current,
write, read, pointer, allocated, freed, fault, kernel); panels as acme
windows; Go Mono for the machine and Go for the narrator; motion as whole
frames at 60 fps. design/mock/gen.py redraws the mocks from the tokens.
|