Concurrency Debugging Purpose Guide agents through diagnosing and fixing concurrency bugs: reading ThreadSanitizer race reports, using Helgrind for lock-order analysis, detecting deadlocks with GDB thread inspection, identifying common misuse patterns, and applying happens-before reasoning in C++ and Rust. Triggers - "ThreadSanitizer reported a data race — how do I read the report?" - "My program deadlocks — how do I debug it?" - "How do I use Helgrind to find threading bugs?" - "Am I using std::atomic correctly?" - "How does happens-before work in C++ memory ordering?" - "How do I find which…