Intel® System Studio
Share information with other developers using Intel® System Studio.

Segmentation Fault starting any System Studio app in Ubuntu 14.04 64-bit VM

Steve_A_2
Beginner
1,079 Views

 

I’m running in a 64-bit Ubuntu 14.04 environment and trying to run this just like we did with the 2015 version and it Segmentation faults.  I even went ahead and created a new VM to make sure there was no conflict with the 2015 version and have the same problem.

 

$:/opt/intel/vtune_amplifier_for_systems$ ./amplxe-vars.sh

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

Intel(R) VTune(TM) Amplifier 2016 for Systems (build 450912)

$:/opt/intel/vtune_amplifier_for_systems$ cd bin64/

$:/opt/intel/vtune_amplifier_for_systems/bin64$ ./amplxe-gui Segmentation fault

 

I tried to run other apps and they Segmentation fault too.  I installed with sudo permissions too.

A co-worker installed on native Ubuntu and said his install is working OK but we have a big need to be using Virtual Machines.

0 Kudos
18 Replies
Jonghak_K_Intel
Employee
1,079 Views

Hi Steve,

 

Thank you for reporting the issue,

could you elaborate more about your VM environment?

There might be a chance to fail to execute System Studio's components because of limitation of your virtual OS's resources.

 

In order to reproduce your situation, please let us know how exactly you setup your VM environment.

 

Thank you

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

Also, please let us know the exact ISS 2015 version of yours.

The installation file name would be enough.

 

Thanks!

0 Kudos
Steve_A_2
Beginner
1,079 Views

Jon -

This is frustrating.  I replied via email on Friday right after getting your replies through email because the support comment link in your emails didn't work and took me to "alien abducted" and "not found" pages but yet I could get to other System Studio posts but not my own...  A couple days later I got replies back saying that the reply email address was an unmonitored box.  Then today I could actually get into my topic and when trying to upload a small picture with the media button (for whatever reason the image button wants a link and not a local image...) it locked IE up and I had to start over.  Yes, I even tried different browsers when I couldn't get to this topic. So, support tools could be a bit better.

Anyway, to answer your questions:

I am using VMware Workstation 10.0.4 build-2249910 from a Windows 7 Enterprise 64-bit (6.1.7601, Service Pack 1) computer with 16GB of memory.

My VM has 9.6 GB allocated to it with 3 processors (I have 4 real cores, no hyper-threading) on a HP Z820 Workstation and the VM has over 150GB of free space so I don't think it is a system resource limitation and I have had System Studio 2015 running here before too.

I am trying to use system_studio_2016.2.037

Do you need anything else or how do we proceed?

 

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

Sorry to hear that Steve,

I will try to reproduce your environment as soon as possible and while we do that, there is something I would like you to get the backtrace log and send it to us.

 

$ ulimit -c unlimited

$ ./amplxe-gui

 

ulimit call must cause core dump when a segmentation fault happens. It will create a file named “core” or “core<smth_else>” in the working directory that can be opened with gdb then. It’s important to analyze it in the same environment where it was dumped, so that the debugger could find all the binaries and maybe symbols.

Run gdb to analyze core:

$ gdb ./amplxe-gui path/to/the/core

 

bt” (backtrace) is the gdb command to get what we want - the stack of the crash.

 

after you get that stack, please attach it to this post.

 

Thanks!

 

 

 

 

0 Kudos
Steve_A_2
Beginner
1,079 Views

Unfortunately, there is No Stack information - attached for your reference

$:/tmp/core_files$ ulimit -c unlimited
$:/tmp/core_files$ /opt/intel/vtune_amplifier_for_systems/bin64/amplxe-gui
Segmentation fault (core dumped)
$:/tmp/core_files$ ls
core.amplxe-gui.2455.1458151034
$:/tmp/core_files$
$:/tmp/core_files$ gdb ./core.amplxe-gui.2455.1458151034
GNU gdb (GDB) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/tmp/core_files/./core.amplxe-gui.2455.1458151034": not in executable format: File format not recognized
(gdb) bt
No stack.

 

0 Kudos
Steve_A_2
Beginner
1,079 Views

Here is the core file for your reference

0 Kudos
Steve_A_2
Beginner
1,079 Views

Note - I am having to use Firefox instead of IE so things work here.

0 Kudos
Steve_A_2
Beginner
1,079 Views

"/tmp/core_files/./core.amplxe-gui.2455.1458151034": not in executable format: File format not recognized
(gdb) bt
No stack.

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

Thank you very much for your cooperation Steve. I sent your results to the engineering and they will take a look.

 

In the meanwhile, I’ve setup the VM environment for myself.

On VM Workstation 12 ( I only could find 12 but could choose VM hardware compatibility with Workstation 10.x ), 4GB RAM, 2 Processors and 20GB memory space.

Downloaded Ubuntu 14.04 iso file and used it to make VM.

I didn’t install any pre-requisites using ‘apt-get install’.

Just installed Intel System Studio 2016 Update 2 for Linux ( system_studio_2016.2.037  )

 

VTune amplifier works fine on my side.  Please find the attached for the environment setup and the result.

 

For the moment, I can’t really tell what might went wrong on your side since we have no back trace and VTune works on my side. You might want to change your VM workstation and give it a try.

Thank you

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

One more update.

The instruction that the engineering team sent me had a mistake.

 

Please try including the executable when running gdb.

gdb /opt/intel/vtune_amplifier_for_systems/bin64/amplxe-gui ./core.amplxe-gui.2455.1458151034

 

 

Then try 'bt' please.

 

Thank you

0 Kudos
Steve_A_2
Beginner
1,079 Views

That worked better.

(gdb) bt
#0  0x00000000004aa7c0 in ?? ()
#1  0x0000000000438a8f in ?? ()
#2  0x00007f1a8b7edef5 in wxEvtHandler::ProcessEvent(wxEvent&) ()
   from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#3  0x00007f1a8b83bc18 in wxWindow::GTKProcessEvent(wxEvent&) const ()
   from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#4  0x00007f1a8b83d4ce in ?? () from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#5  0x00007f1a885b53b8 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x00007f1a885c6d3d in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x00007f1a885cea29 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x00007f1a885cece2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x00007f1a89894640 in gtk_widget_realize () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#10 0x00007f1a89894828 in gtk_widget_map () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#11 0x00007f1a8b838d59 in ?? () from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#12 0x00007f1a885b555f in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007f1a885ce088 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007f1a885cece2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007f1a898947fe in gtk_widget_map () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16 0x00007f1a898a4c92 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#17 0x00007f1a885b55e7 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007f1a885ce088 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007f1a885cece2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007f1a898947fe in gtk_widget_map () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#21 0x00007f1a8989ee5e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#22 0x00007f1a885b53b8 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x00007f1a885c6557 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x00007f1a885cea29 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x00007f1a885cece2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x00007f1a89893dc6 in gtk_widget_show () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#27 0x00007f1a8b84007a in wxWindow::Show(bool) () from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#28 0x00007f1a8b835abd in wxTopLevelWindowGTK::Show(bool) () from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#29 0x00007f1a8b9c7592 in wxSplashScreen::wxSplashScreen(wxBitmap const&, long, int, wxWindow*, int, wxPoint const&, wxSize const&, long) ()
   from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#30 0x000000000043c6a0 in ?? ()
#31 0x00007f1a8b79a9ce in wxEntry(int&, char**) () from /opt/intel/vtune_amplifier_2016_for_systems.2.0.450912/bin64/../lib64/libwx_gtk2-2.8.so.0
#32 0x0000000000437a4d in ?? ()
#33 0x00007f1a8a25aec5 in __libc_start_main (main=0x437a10, argc=1, argv=0x7fffca021418, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffca021408) at libc-start.c:287
---Type <return> to continue, or q <return> to quit---
#34 0x0000000000426b99 in ?? ()
#35 0x00007fffca021408 in ?? ()
#36 0x000000000000001c in ?? ()
#37 0x0000000000000001 in ?? ()
#38 0x00007fffca022fd2 in ?? ()
#39 0x0000000000000000 in ?? ()
 

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

Hi Steve,

 

From investigating your back log, the engineering team figured out that there's a problem with GUI compatibility with your Ubuntu, so suggested to try the following :

  1. changing Ubuntu Appearance theme to any other (this must be in settings\appearance\themes)

  2. if “a)” it doesn’t help - try switching from GTK to KDE (as far as I understand this can be done by installing kubuntu-desktop

 

Please try and let us know how it goes.

 

THank you!

0 Kudos
Steve_A_2
Beginner
1,079 Views

I am using gnome (flashback metacity) because it is faster, not unity so I don't have themes (that I could find anyway).  I switched to unity and with both the default theme and radiance I still get segmentation faults.  I cannot change to KDE since it wants to uninstall my development tools.

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

Will get back with another solution after investigating more.

 

Thank you

0 Kudos
Steve_A_2
Beginner
1,079 Views

To be clear, I didn't have any problems running Intel System Studio 2015 in this environment and this issue is new to 2016.

0 Kudos
Jonghak_K_Intel
Employee
1,079 Views

Hi Steve,

 

could you let me know which update version of ISS 2015 you used last time?

EX) Intel System Studio Update 2

That would help us find what is blocking more quickly.

 

Thank you

0 Kudos
Steve_A_2
Beginner
1,079 Views

l_cembd_p_2015.0.030.tgz

0 Kudos
Steve_A_2
Beginner
1,079 Views

I created a new temporary 14.04 VM (I can’t use this VM since our image has changes I need for development) and it works there with Workstation 10.x.x so it isn't a workstation problem.

0 Kudos
Reply