amplxe-gui : segmentation fault on startup

[Alexis_R_]

First time user of the amplifier here. Apologies if this is a FAQ.

When running amplxe-gui, the splash screen comes up for a split second, and I then get Segmentation fault.

$ amplxe-gui
Segmentation fault

This is a fresh install without root privileges. Here are some details about the install and the system (edited hostname):

$ uname -a
Linux host.name.edu 2.6.18-308.16.1.el5 #1 SMP Tue Sep 18 07:21:07 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/redhat-release
Red Hat Enterprise Linux Client release 5.8 (Tikanga)

$ cat /proc/cpuinfo | grep Xeon | tail -1
model name      : Intel(R) Xeon(R) CPU           X5690  @ 3.47GHz

$ amplxe-cl --version
Intel(R) VTune(TM) Amplifier XE 2013 Update 7 (build 288061) Command Line Tool

Please advise how to proceed from there or if you need more info. Thanks.

[Bernard]

It seems that error occurres during the instalation(registration) phase of the software.

[Michael_B_13]

Thank you Robert. Then I'll have to wait for a fix and meanwhile have to search other work until I have the Amplifier again.

[Bernard]

I still suspect that the segfault is related to dereferencing pointer to char.

[Michael_B_13]

Today I installed Update 10 for vtune Amplifier and the error is still the same...

[Michael_B_13]

After completely uninstalling vtune (their were some files left in the /opt/intelvtune... folder which I had to remove by hand and installing update 10 again the software runs. This was a hint by the premier support from Intel.

Thanks to all for help.

[robert-reed]

I'm happy that you found a solution, and sorry that it didn't occur to me to suggest such a ream and reinstall to you ealier.  I've seen examples of such "toxic remainders" in previous versions of the installer, and the method you describe of uninstalling and clearing any remaining detritus before reinstalling has been a common approach to resolve this situations. However, since I did not have similar trouble when trying to reproduce the conditions  you experienced, and "knew" that the previous problems had been fixed in a previous release, the thought to suggest this technique never even occurred to me.  I'm glad you were able to discover the method independently and that it was effective.  Happy performance analyzing!

[Bernard]

Glad that you solved installation problems.

[King_Crimson]

Many thanks! This solves the annoying "segmentation fault" problem that occurs on my machine. The important step is to entirely remove the vtune folder and have a fresh reinstallation.

Michael B. wrote:

After completely uninstalling vtune (their were some files left in the /opt/intelvtune... folder which I had to remove by hand and installing update 10 again the software runs. This was a hint by the premier support from Intel.

Thanks to all for help.

[AndrewC]

I am getting the identical issue with Inspector-XE GUI. Uninstalling fixed the issue.

[vkeller]

Dear all,

It seems that this issue has been fixed by many of you. Nevertheless, all the proposed solutions did not work for me thus I investigated more deeper. I suspected a problem with another package on my system.

System : Mint LMDE (should also work on Debian Testing)
Amplifier XE version : 

Intel(R) VTune(TM) Amplifier XE 2015 (build 367959) Command Line Tool
Copyright (C) 2009-2014 Intel Corporation. All rights reserved.

Like everybody I got the trace :

#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:31
#1  0x00007ffe61299d86 in __GI___strdup (s=0x51 <Address 0x51 out of bounds>) at strdup.c:41
#2  0x00007ffe584efcb6 in ?? () from /lib/x86_64-linux-gnu/libudev.so.1
#3  0x00007ffe584f17f9 in ?? () from /lib/x86_64-linux-gnu/libudev.so.1
#4  0x00007ffe584f1a94 in udev_device_new_from_syspath () from /lib/x86_64-linux-gnu/libudev.so.1
#5  0x00007ffe5031e51f in ?? () from /lib/x86_64-linux-gnu/libudev.so.0
#6  0x00007ffe5031e73e in ?? () from /lib/x86_64-linux-gnu/libudev.so.0
#7  0x00007ffe5031e9bd in ?? () from /lib/x86_64-linux-gnu/libudev.so.0

...

#36 0x00007ffe626cc828 in wxEntry(int&, char**) () from /opt/intel/vtune_amplifier_xe_2015.1.0.367959/bin64/../lib64/libwx_gtk2-2.8.so.0
#37 0x000000000042bdbb in ?? ()
#38 0x00007ffe61237995 in __libc_start_main (main=0x42bd80, argc=1, ubp_av=0x7fff9f595e38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9f595e28)
    at libc-start.c:276
#39 0x0000000000423429 in ?? ()
#40 0x00007fff9f595e28 in ?? ()
#41 0x0000000000000000 in ?? ()

Line number 36 gave me the hint to have a look into the packages related to wx (wxWidgets). Using deborphan I got 4 orphans :

  libwxbase2.8-0 libwxbase3.0-0 libwxgtk2.8-0 libwxgtk3.0-0

that I removed. Restart amplxe-gui with success !

Hope it helps others

Cheers, Vince

[Vitaly_S_Intel]

Hi Vince!

Thanks for your message and useful details! I'll check how these packages affect VTune GUI and we'll try to resolve that issue.

Through the root cause of your problem differs with described in this long thread. Update issue mentioned here above should be completely fixed in VTune Amplifier XE 2015.

[Deepak_S_2]

Hello Sir ,

When I am profiling any application it profiles correctly with results generated in the window.But gettimg following lines in terminal:

** (amplxe-gui:7206): CRITICAL **: os_bar_hide: assertion `OS_IS_BAR (bar)' failed

(amplxe-gui:7206): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

** (amplxe-gui:7206): CRITICAL **: os_bar_set_parent: assertion `OS_IS_BAR (bar)' failed

** (amplxe-gui:7206): CRITICAL **: os_bar_hide: assertion `OS_IS_BAR (bar)' failed

(amplxe-gui:7206): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

** (amplxe-gui:7206): CRITICAL **: os_bar_set_parent: assertion `OS_IS_BAR (bar)' failed
init done
opengl support available..

Please help what happened wrong.

Thanks in advance.

[Vitaly_S_Intel]

You can ignore them. They're caused by VTune GUI front-end (wxWidgets). Our validation shows these messages actually do not cause any issues.