How do you prove a thread pool correct with sanitizers and unit tests?

A strong answer

A strong candidate frames How do you prove a thread pool correct with sanitizers and unit tests? around the exact memory layout, compiler semantics, and hardware execution model covered in Sanitizers and Tests: Proving the Pool Correct. Run address plus undefined and thread builds, assert single execution and drain, and read reports to file and line.

Threaded code can pass repeated runs while harboring a race. Timing hides the interleaving, the counter lands correctly by luck, and shutdown joins cleanly because the waiter happened to arrive last. Production load changes timing and the fault surfaces as a drifted total, a crash in a worker, or a hang on stop. The trace above shows the deterministic counterpart: submit, wait and assert single execution, so the expected outcome is explicit rather than inferred from silence.

A sanitizer build instruments the binary to report memory and threading faults with stacks. A unit test drives the pool through fixed scenarios with assertions. Instrumentation finds the fault location, tests prevent regression once the fix lands.

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

• Mastery of core invariant: Run address, thread and undefined sanitizers on threaded code.
• Mastery of core invariant: Write deterministic unit tests for task queues and shutdown.
• Mastery of core invariant: Interpret sanitizer reports to locate races and lifetime faults.
• Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
• Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

• Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
• Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.