Joseph Ferano
2e203f64b8
The INSERTIONSORT crash, all three rulings (FIX.org 2026-09-20): - (bytes s) allocates a writable copy through the allocator surface — context or (bytes s a), StorageExhausted with retry, a registry note in dev builds (flan_bytes_dup, lowered like vec-new). (bytes-view s) is the old zero-cost reinterpret, renamed, read-only by convention; every in-repo reader swept over to it. (string b) unchanged. - String constants were already read-only on both backends at -O0; now pinned — bytes-copy.flan rows on LLVM/-O0/--x86, and dies_segv rows asserting the write-through-view trap on both backends. - A dev build installs a SIGSEGV/SIGBUS handler by the same dev-only constructor slot that arms the registry: one line naming the address and the innermost frame, then the trap-hook park — stopped, not dead, the daemon serving. No agent: message and re-raise. Release builds untouched. Pinned by trap_park over dev-segv.flan.
18 lines
853 B
Plaintext
18 lines
853 B
Plaintext
;;;; The dogfooding crash, replayed on purpose: a write through a bytes-view
|
|
;;;; of a string literal lands in read-only memory and takes SIGSEGV. In a
|
|
;;;; dev session that used to kill the whole process — daemon, compiler and
|
|
;;;; socket together, with no message at all. The dev build's crash handler
|
|
;;;; turns it into the same park the no-channel traps take: one line naming
|
|
;;;; the address and the frame, then the break loop, with the daemon alive
|
|
;;;; and answering behind it. There is no restart to list — a faulting
|
|
;;;; instruction has nowhere to resume at — which is the same empty-list
|
|
;;;; shape dev-trap-null-alloc.flan pins for free-all.
|
|
(import agent "vendor:agent")
|
|
|
|
(defn main [] i32
|
|
(agent/start "/tmp/flan-dev-segv-fallback.sock")
|
|
(let [v (bytes-view "INSERTIONSORT")]
|
|
(set (at v 0) \Z)
|
|
(print (string v))
|
|
0))
|