try valgrind

Author: majosm

.github/workflows/ci.yml

@@ -127,8 +127,27 @@ jobs:
                 curl -L -O https://tiker.net/ci-support-v0
                 . ./ci-support-v0
                 build_py_project_in_conda_env
+
+                # Capture the heap-corrupting write directly with valgrind. The
+                # Intel CPU OpenCL runtime corrupts the host heap during kernel
+                # execution; faulthandler only shows where the corruption later
+                # detonates (often in unrelated code), not the bad write itself.
+                # valgrind traps the invalid write at the instant it happens, even
+                # inside the closed-source libintelocl.so.
+                #
+                #  - PYTHONMALLOC=malloc routes CPython allocations through libc so
+                #    valgrind isn't drowned in pymalloc false positives.
+                #  - --smc-check=all-non-file: the runtime JITs kernels into
+                #    non-file-backed memory; without it valgrind may run stale
+                #    translations of the generated code.
+                sudo apt-get update && sudo apt-get install -y valgrind
+                export PYTHONMALLOC=malloc
                 export NO_COLOR=1
-                python intel_crash_reproducer.py
+                valgrind \
+                    --smc-check=all-non-file \
+                    --leak-check=no --errors-for-leak-kinds=none \
+                    --error-exitcode=1 \
+                    python intel_crash_reproducer.py
 
     examples3:
         name: Examples Conda Py3