In the project I'm working on, at the moment we have an unknown number of flickering tests that fail at different rates (anywhere, every time, every time every 5000 starts), which made us believe that we have have serious Heisenbugs Allow. Most of the time, including tracing instructions in the code, change the time frame sufficient to eliminate these errors, or at least make them less common, but obviously this is a wrong error correction.
We are wondering if there are any tools similar to CHESS (http://research.microsoft.com/en-us/projects/chess/download.aspx) that work in Visual Studio 2010 for stress testing applications and determine potential race conditions and deadlocks
Pete martin
source share