Analyzers
Support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
4682 Discussions

Intel Thread Checker hungs on start

hitfounder
Beginner
196 Views
I try to use Intel Thread Checker but can't check even samples. Then I try to folow getting started guide and perform "tcheck_cl ./primes.gcc" Thread Checker hungs just after two strings:
"Intel Thread Checker 3.1 command line instrumentation driver (27583)
Copyright (c) 2007 Intel Corporation. All rights reserved."

I use Intel Thread Checker 3.1_012 for Linux. Operating system is Ubuntu 8.10 server clear setup. Cpu is Intel Core Duo E2160
0 Kudos
1 Solution
ymost
New Contributor I
197 Views
Quoting - hitfounder
I try to use Intel Thread Checker but can't check even samples. Then I try to folow getting started guide and perform "tcheck_cl ./primes.gcc" Thread Checker hungs just after two strings:
"Intel Thread Checker 3.1 command line instrumentation driver (27583)
Copyright (c) 2007 Intel Corporation. All rights reserved."

I use Intel Thread Checker 3.1_012 for Linux. Operating system is Ubuntu 8.10 server clear setup. Cpu is Intel Core Duo E2160

I had the same problem, and it was solved by using the "--noinstrument" flag with tcheck_cl.

Hope this helps.

View solution in original post

5 Replies
TimP
Black Belt
197 Views
Quoting - hitfounder
I try to use Intel Thread Checker but can't check even samples. Then I try to folow getting started guide and perform "tcheck_cl ./primes.gcc" Thread Checker hungs just after two strings:
"Intel Thread Checker 3.1 command line instrumentation driver (27583)
Copyright (c) 2007 Intel Corporation. All rights reserved."

I use Intel Thread Checker 3.1_012 for Linux. Operating system is Ubuntu 8.10 server clear setup. Cpu is Intel Core Duo E2160
Parallel Studio is a Windows tool. There are more suitable forum sections for linux Thread Checker, although the best choice might depend on which other Intel software tools you use in association with Thread Checker. If using Intel compilers, the re-compilation with -tcheck option (setting both tcheck and compiler environment variables) is more reliable than instrumentation driver.
Peter_W_Intel
Employee
197 Views
Quoting - hitfounder
I try to use Intel Thread Checker but can't check even samples. Then I try to folow getting started guide and perform "tcheck_cl ./primes.gcc" Thread Checker hungs just after two strings:
"Intel Thread Checker 3.1 command line instrumentation driver (27583)
Copyright (c) 2007 Intel Corporation. All rights reserved."

I use Intel Thread Checker 3.1_012 for Linux. Operating system is Ubuntu 8.10 server clear setup. Cpu is Intel Core Duo E2160
Ubuntu* is not supported Operating System in Intel? Thread Checker v3.1_012's release notes. Possibly it misses some utilities I suspect. Would you please try it on supported RedHat* OS or SUSE* OS?

By the way, have you done "source /opt/intel/itt/tchecker/bin/32(e)/tcheck_vars.sh" before running tcheck_cl?

Regards, Peter
ymost
New Contributor I
198 Views
Quoting - hitfounder
I try to use Intel Thread Checker but can't check even samples. Then I try to folow getting started guide and perform "tcheck_cl ./primes.gcc" Thread Checker hungs just after two strings:
"Intel Thread Checker 3.1 command line instrumentation driver (27583)
Copyright (c) 2007 Intel Corporation. All rights reserved."

I use Intel Thread Checker 3.1_012 for Linux. Operating system is Ubuntu 8.10 server clear setup. Cpu is Intel Core Duo E2160

I had the same problem, and it was solved by using the "--noinstrument" flag with tcheck_cl.

Hope this helps.
hitfounder
Beginner
197 Views
Quoting - ymost

I had the same problem, and it was solved by using the "--noinstrument" flag with tcheck_cl.

Hope this helps.

Thanks a lot, it helps.
Vladimir_T_Intel
Moderator
197 Views
Quoting - ymost
I had the same problem, and it was solved by using the "--noinstrument" flag with tcheck_cl.


But this option switches off the binary instrumentation of Thread Chacker, which means you won't collect useful results. In this case youmight want to use source level instrumentation (-tcheck option)during compilation with Intel compiler.
Reply