Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
5105 Discussions

Inspector XE 2013 Update 9 SIGSEGV on startup

AndrewC
New Contributor III
544 Views

I can't run Inspector XE 2013 Update 9 GUI.

I am running on CentOS 6. Othe lintel tools such as ampl-xe-gui run fine.Any ideas?

 

Program received signal SIGSEGV, Segmentation fault.
0x00002aaaac120a45 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
   from /opt/intel/inspector_xe_2013/bin64/../lib64/libinspxe_cfgmgr_2.19.so
(gdb) bt
#0  0x00002aaaac120a45 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
   from /opt/intel/inspector_xe_2013/bin64/../lib64/libinspxe_cfgmgr_2.19.so
#1  0x00002aaaac120806 in cfgmgr2::IConfigDescriptorRegistry::create(cfgmgr2::config_type_t, gen_helpers2::sptr_t<cfgmgr2::IContextValueMap const>)
    () from /opt/intel/inspector_xe_2013/bin64/../lib64/libinspxe_cfgmgr_2.19.so
#2  0x00002aaab31b3e94 in client_2_7_41::xe::loader::cmdmgr_t::get_all_run_commands() const ()
   from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#3  0x00002aaab31befbb in client_2_7_41::cmn::loader::cmdmgr_t::get_mru_run_commands() const ()
   from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#4  0x00002aaab31beded in client_2_7_41::cmn::loader::cmdmgr_t::prepare_mru_commands(eil1::ICommands*, unsigned int, unsigned int, client_2_7_41::cmn::loader::runcmd_info_t::run_command_type_t) () from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#5  0x00002aaab31b3b65 in client_2_7_41::xe::loader::cmdmgr_t::refresh_quick_start_commands() ()
   from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#6  0x00002aaab31c15d1 in client_2_7_41::cmn::loader::cmdmgr_t::initialize(eil1::IDE_Env*) ()
   from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#7  0x00002aaab31ba61c in client_2_7_41::xe::loader::ide_proxy_callback_t::initialize(eil1::IDE_Env*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#8  0x00002aaab31aab97 in StartUp () from /opt/intel/inspector_xe_2013/lib64/libinspxe_client_loader_2.7.so
#9  0x00000000004456cf in ?? ()
#10 0x000000000045ff5c in ?? ()
#11 0x000000000041f581 in ?? ()
#12 0x00002aaaab2621b4 in wxEntry(int&, char**) () from /opt/intel/inspector_xe_2013/bin64/../lib64/libwx_gtk2-2.8.so.0
#13 0x000000000041b50b in wxPanel::Init() ()
#14 0x0000003e1141d9c4 in __libc_start_main () from /lib64/libc.so.6
#15 0x000000000041b40a in wxPanel::Init() ()
#16 0x00007fffffffe078 in ?? ()
#17 0x0000000000000000 in ?? ()

0 Kudos
5 Replies
AndrewC
New Contributor III
544 Views

And yes, I did delete ~/.intel/inspxe before running.

0 Kudos
AndrewC
New Contributor III
544 Views

OK, solved my own problem based on a thread for Amplifier

Need to completely uninstall and remove all previous installations of inspector-xe, then re-install.

0 Kudos
Peter_W_Intel
Employee
544 Views

Installer will detect prior version when you install a new version. So deleting Inspector_XE_2013 is not good for resinatlling the new update. It's OK that you have to uninstall the prior product first, however if *uninstaller* or its components are demanaged, here is my tip to install new update.

1. Use "rpm -qa intel-insp*" to detect remained prior product.

intel-inspector-xe-cli-common-328075-13.1-9.noarch
intel-inspector-xe-gui-328075-13.1-9.x86_64
intel-inspector-xe-cli-328075-13.1-9.i486
intel-inspector-xe-doc-328075-13.1-9.noarch
intel-inspector-xe-cli-pset-328075-13.1-9.noarch
intel-inspector-xe-cli-328075-13.1-9.x86_64
intel-inspector-xe-gui-common-328075-13.1-9.noarch

2. Use "rpm -e" to remove them one by one.

3. Delete Inspector XE folder manually.

4. Then install new update.
 

0 Kudos
Bernard
Valued Contributor I
544 Views

>>>0x00002aaaac120a45 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
   from /opt/intel/inspector_xe_2013/bin64/../lib64/libinspxe_cfgmgr_2.19.so>>>

Could this function be responsible for SIGSEGV?

0 Kudos
AndrewC
New Contributor III
544 Views

I had done a proper install of Intel Composer XE 2013 SP1 Update 2 prior to this.

The problem remained.

The solution was to

- run uninstall.sh from the Intel Inspector XE directory

- delete the directory completely

- reinstall Inspector XE

 

Please read this thread regarding the identical issue with Ampl XE

http://software.intel.com/en-us/forums/topic/393354

 

 

0 Kudos
Reply