Rongsong Shen
02e9275706
/xce-build now takes a build PROFILE: asan (default, debug+ASAN -> xce.build, backward-compatible), debug (non-ASAN -O0 -g3 -fno-inline -fno-omit-frame-pointer -> build.dbg, for gdb/cores), release (-O3 -> build.release). Each profile uses its own default build dir so variants don't clobber each other; arg2 may still be a legacy build_dir. asan runs the unit suites; debug/release are build-only (the suites are ASAN-oriented and the meson test harness is overlay-fs fragile, bug-924) and print how to run a suite directly. Why: bug-1282/bug-1286 are heisenbugs ASAN perturbs away (no SIGSEGV) and that gdb-on-release turns into a hang/timeout. The non-ASAN -O0 -g3 build reproduces them AND yields a symbolized backtrace under gdb. It immediately paid off: the debug profile ROOT-CAUSED bug-1286 (the round-4 segfault) — myreq_handler (cluster.c:251) does `c = ep->owner` then `ha_dispatch_gate(&c->ha,…)`; on chaotic restart a walCatchupEntry (op 37) vtask runs with ep->owner==NULL, so &c->ha = 0x3ff0 -> deref crash at ha.c:3194. Fix is a NULL-guard in myreq_handler (+ owner-lifecycle). 7.2 now has one remaining blocker (bug-1286, root-caused); bug-1282 deadlock is fixed. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019dbTHR9CsEYK9RsqmQpQpC |
||
|---|---|---|
| .. | ||
| appimage | ||
| deploy-ha.sh | ||
| go_build | ||
| test-commit-durability.sh | ||
| test-heartbeat-tolerance.sh | ||
| xce-build.sh | ||