Inspector XE Client - not able to run

Inspector XE Client - not able to run

I am able to run the inspxe-cl in my server machine based on Centos 5.4 (Linux dt05 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux). The same i try to run on my development setup, which is a stripdown version of the same Centos 5.4. I am not able to run the inspxe-cl, it throws out the error below.

[admin@at02 ~]# inspxe-cl -c

Error: Unknown option: -c

Can someone help me in identifying the issue?


I didnt see any library issue in the dev setup. Ldd output attached below. => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea4b48000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea4d47000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea4e7f000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5016000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5124000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5374000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea558e000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea56b2000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5813000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5931000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5d2b000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5e39000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea5f78000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea60a6000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea61fa000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea630e000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea64a2000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea6705000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea692f000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea6b4a000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea6c69000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea6ebe000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea6fc5000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea715f000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea728c000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea739f000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea753c000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea7651000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea77dd000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea7a6e000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea7beb000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea7d09000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea7e22000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea7f4e000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea80a8000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea81c1000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea82c7000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x00002b8ea84e3000) => /lib64/ (0x00002b8ea85f5000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x0000003fe9e00000) => /opt/intel/inspector_xe_2011/bin64/../lib64/ (0x0000003fe9a00000) => /lib64/ (0x00002b8ea8879000) => /lib64/ (0x00002b8ea8bd1000) => /lib64/ (0x00002b8ea8dd5000) => /opt/intel/inspector_xe_2011/bin64/../lib64/../lib64/ (0x00002b8ea8ff2000) => /opt/intel/inspector_xe_2011/bin64/../lib64/../lib64/ (0x00002b8ea9111000) => /opt/intel/inspector_xe_2011/bin64/../lib64/../lib64/ (0x00002b8ea926a000) => /opt/intel/inspector_xe_2011/bin64/../lib64/../lib64/ (0x00002b8ea94a1000)

/lib64/ (0x00002b8ea4b2a000)

5 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.


Thank you for
contacting Intel in regards to the inspxe-cl behavior you have experienced. Can you let me know the outcome of inspxe-cl
run by itself and inspxe-cl -version ? Was this working before or is this a new
install? This will help determine the
scope of the issue.



This is a new install. I remember having it run with the update1. But i dont have the installation files for it now.Below are the output taken from the Dev machine. The version option also gave the same error.


[admin@at02 tools]# /opt/intel/inspector_xe/bin64/inspxe-cl

Intel Inspector XE 2011 Update 6 (build 186554) Command Line tool

Copyright (C) 2009-2011 Intel Corporation. All rights reserved.

Usage: inspxe-cl <-action> [-action-option] [-global-option] [[--] target [target options]]

Type 'inspxe-cl -help ' for help on a specific action.


1) Run the 'Locate Deadlocks and Data Races' analysis on target myApp

and store result in default-named directory, such as r000ti3.

inspxe-cl -collect ti3 -- myApp

2) Run the 'Locate Memory Problems' analysis on target myApp; do

not include in problem summary any problems that match rules in suppression

file mySup.sup; store result in directory myRes.

inspxe-cl -c mi3 -suppression-file mySup -r myRes -- myApp

3) Display list of available analysis types and preset configuration levels.

inspxe-cl -help collect

Use -help for more detailed help.


[admin@at02 tools]# /opt/intel/inspector_xe/bin64/inspxe-cl -version

Error: Unknown option: -version


Thank you for the additional information. It seems there may be an incompatibility or incomplete installation
issue. You also mentioned that you are
running with a stripped down version of Centos 5.4 which may be problematic.

Intel Inspector XE 2011 Update 6, per the release
notes supports CentOS* 5.6. Intel
Inspector XE 2011 Update 7 supports CentOS* versions equivalent to Red Hat*
Enterprise Linux* versions supported for the update which are Red Hat*
Enterprise Linux* 4.9, 5.6 and 6.1.

To trouble shoot this further, Can you run the Amplifier
feedback report and attach the results to the case? This report will provide us with information
about the system to further trouble shoot the root cause.

$ inspxe-feedback -report-system-info > info.txt

Then upload the info.txt file to this forum thread. At your discretion, you may wish to make the
thread private at that time.

Also, just in case, can you check to make sure no error
is thrown to the system logs?

Install logging may provide some information. Can you check /tmp or equivalent for recent log
files which contain issa or pset in the file name.


Will take this tread private via internal case

Leave a Comment

Please sign in to add a comment. Not a member? Join today