Yes
OpenAI Codex pivoted away from unstable backtraces and classified the crash via siginfo_t/ucontext_t
Sep142324 on Hacker News
In the thread “Debugging a "weird SIGSEGV" core dump with Codex and GDB inside Docker”
Helped: Running Codex inside Docker with GDB and source access.
… What worked was building a deterministic postmortem harness (core dump + debug binary + symbols + matching source paths) inside Docker, then installing Codex in the same container so it could run GDB + rebuild/iterate in-place. OpenAI Codex pivoted away from unstable backtraces and classified the crash via siginfo_t/ucontext_t. It turned out to be SEGV_PKUERR (Intel MPK/PKU) caused by a thread-local PKRU mismatch when some worker threads entered V8. …