data races

Using Intel® Inspector XE 2011 to Find Data Races in Multithreaded Code

Intel Inspector XE 2011 automatically finds memory errors, deadlocks and other conditions that could lead to deadlocks, data races, thread . Some specific issues associated with debugging multithreaded applications will be discussed in this article.
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Начинающий
  • Intel® Parallel Studio
  • Intel® Parallel Studio XE
  • Intel® Inspector XE
  • Intel® Parallel Inspector
  • critical section
  • data races
  • Learning Lab
  • OpenMP*
  • Параллельные вычисления
  • Многопоточность
  • Report Data Races Error in User Synchronization itself?

    Intel® Thread Checker can check data races on sharing variables by using user's primitive, but how about user's primitive itself?
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Intel® Thread Checker
  • thread checker
  • data races
  • ittnotify
  • User Synchronization
  • When test suites fail us (when they meet parallelism).

    Another week and another customer shared how messed up their test suites were because of parallel programming. So where are we going wrong?

    First, it is natural to feel confused and disoriented when a failure "escapes" into the wild.  In other words, when a bug is not caught by our test suites it is natural to DEMAND an plan to correct this failure!

    Second, it is common to fall back on a simple belief: an "escape" means we need MORE tests.

    This is where parallelism trips us up.

    Interview with Dmitriy Vyukov - the author of Relacy Race Detector (RRD)

    This is an interview with Dmitriy Vyukov - the author of Relacy Race Detector (RRD) tool intended for verifying parallel applications. In this article you will learn about the history of creating RRD and its basic abilities.
  • lock-free
  • data races
  • Параллельные вычисления
  • Don't rely on memory barriers for synchronization... Only if you don't aware of Relacy Race Detector!

    Multithreading is hard. Implementation of synchronization primitives is even harder. And most advanced synchronization primitives which exploit relaxed memory models are brain damaging.  So don't rely on memory barriers for synchronization. Now you will think "Ah, you are one of those folks, who constantly saying to us - don't do this, don't do that, it's too difficult, it's too dangerous, anyway you will fail". Nope, I am not. I am saying exactly the opposite - do rely on memory barriers for synchronization...

    Подписаться на data races