;;;; 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))