Nishi Family › Compare › Debugging and Diagnosis (Doctor)

Nishi vs the Field

Debugging and Diagnosis (Doctor) — mechanically measured, liar-killed, sovereign.

Nishi vs rr and GDB and Delve and C-Vise

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.
CapabilityNishirrGDBDelveC-ViseNotes
Per-function miscompile bisection (names the breaker)YesNoNoNoPartFunction-splice frankenbuilds isolate the guilty codegen; C-Vise reduces INPUTS, ours bisects FUNCTIONS -- complementary halves
Compile-fail diagnosis in one stepYesNoNoNoNoRe-runs the compiler with stderr VISIBLE and prints the real error (the empty-.s trap is usually a muted source error); the wrapper now self-diagnoses too
Codegen-shape fuzz generationYesNoNoNoPartShape-axis generator found a real nx_cc bug (about 1500 early-exit blocks = empty .s, 2026-07-05)
Permanent regression witnesses (probe organs)YesNoNoNoNoEvery pinned bug becomes a tiny organ that re-runs forever; nx_probe_ctor re-verified the enum-ctor SIGSEGV FIXED 2026-07-09; nx_probe_float still honestly RED
Living trap register (T# taxonomy)YesNoNoNoNoEvery debugging war ends in a T#-tagged register entry with the diagnosis path -- the raw material of the make-it-unrepresentable ladder
Autonomous health witnessYesNoNoNoNoGenerate-build-verify witness runs autonomously (exec engine 3/3, 2026-07-06); a compiler regression is an ALARM, not a surprise
Breakpoint debugger (step, inspect, frames)NoYesBestYesNoGDB is the bar; we have NO interactive debugger at all -- printf-and-bisect is the story
Record-replay time-travel debuggingNoBestPartNoNorr 5.9.0 is the bar (reverse execution over recorded traces); nothing sovereign records execution
Watchpoints and memory breakpointsNoYesBestPartNoGDB hardware watchpoints are the bar; our memory bugs are hunted by canary prints
DWARF / source-line debug infoNoYesYesYesNoTHE root blocker: emitted ELFs carry no line mapping, so even the field's debuggers cannot help on our binaries
Test-case reduction at scaleNoNoNoNoBestC-Vise is the bar; our reductions are hand-swept thresholds (shapeprobe N-sweeps)
Core-dump / crash analysisNoPartBestPartNoGDB post-mortem is the bar; our crashes are exit-code + last-print forensics
Remote / attach debuggingNoPartBestYesNogdbserver is the bar; our remote diagnosis is log tails over the mgmt API
IDE debug protocol (DAP)NoNoPartBestNoDelve powers VS Code Go debugging; ties to the lang census LSP gap
LLM-assisted debugging and repairNoNoNoNoNoThe cross-roster convergence gap (lang mom 145, janitor mom 111); nobody in THIS field ships it either yet
Diagnosis wired into the self-healing loopBestNoNoNoNoFuzz (shapeprobe) to detect (equiv oracle) to bisect (splice) to immunize (probe organ) to bless (never-brick install) -- ONE in-substrate circuit; the field's tools are islands a human ferries between
Every fixed bug becomes a permanent witnessBestNoNoNoNoImmunization by construction: the probe that pinned the bug re-runs on every sweep forever -- fixed classes cannot silently regress; the field closes tickets
coverage 470/1000EXCEEDS 2PRESENT 6ABSENT 9
Honest verdict. The Nishi doctor is a DIAGNOSIS-AND-IMMUNIZATION culture rather than a debugger: when something breaks, the splice bisector names the guilty function, ccdiag surfaces the muted compiler error in one step, the shape prober fuzzes for the class, the fix lands, and a permanent probe organ re-runs forever so the class can never silently return (the enum-ctor probe re-verified its bug FIXED on 2026-07-09, two weeks after filing). What it does NOT have is the field's entire interactive half: no breakpoint debugger, no record-replay time travel (rr is the bar), no watchpoints, no core-dump analysis, no remote attach, no DAP protocol -- and the root blocker is that emitted ELFs carry no DWARF at all, so even GDB cannot help; printf-and-bisect is the honest debug story. The climb: DWARF line tables in the backends first (it unlocks the whole field's tooling for free), then a minimal sovereign breakpoint runner, then input reduction at C-Vise scale.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/doctor.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.