Find race conditions and deadlocks in your code.
Guides diagnosis and repair of data races, deadlocks, and memory-ordering bugs in C++ and Rust.
When to use it
Use when interpreting race reports, investigating deadlocks, checking atomic operations, or reasoning about memory ordering.
It changes how the agent diagnoses and fixes concurrency bugs in project code.
What you provide
The Helgrind workflow uses Valgrind to run the program and detect threading problems.
The deadlock-inspection workflow uses GDB to attach to the program and inspect its threads.
No additional actions listed.