This getting started guide takes you through all the basic steps required to prepare your threaded software for data collection,and then generate and analyze data using Intel® Thread Checker for Windows*.
This is a known technical limitation in the current version of Intel® Thread Checker for Windows*.
These are related to DllMain and loader lock. DllMain is serialized internally by Microsoft Windows* using the loader lock. However, Intel® Thread Checker is not able to model the loader lock because it is invisible to the application
Whenever a thread is created or terminated, the DllMain is called and these errors are generated. These errors are not generated at startup phase.
This release does not support Unicode file names.
Intel® Thread Checker for Linux* does not support binary instrumentation on Intel® Itanium platforms.
Intel® Thread Checker may face some incompatibility issues with lguide library provided by older version of Intel® Math Kernel library. Please upgrade to the latest version of Intel® Math Kernel library for Linux* (8.0 and higher) if you encounter error message similar to "undefined references to _kmpc_global_thread_num".
We currently do not support analysis of OpenMP* applications compiled with the Microsoft* Visual Studio* or with GNU C++ Compiler.
This is due to the custom synchronization used by the Microsoft Visual Studio OpenMP runtime library and the GNU C++ Compiler OpenMP runtime library.
The Intel Thread Checker facilitates debugging of multithreaded programs by automatically finding common errors such as storage conflicts, deadlock, API violations, inconsistent variable scope, thread stack overflows, etc. The non-deterministic nature of concurrency errors makes them particularly difficult to find with traditional debuggers. Thread Checker pinpoints error locations down to the source lines involved and provides stack traces showing the paths taken by the threads to reach the error. It also identifies the variables involved.
- 第 7 页