amplxe-gui : segmentation fault on startup

amplxe-gui : segmentation fault on startup

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.

55 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.

Can you post call stack info?

You need to use root privilege to install the tool.

Cita:

Peter Wang (Intel) escribió:

You need to use root privilege to install the tool.

Hi Peter,

The release notes say:

The install can be run as a non-root user, but in this case not all collectors will be available to the user.

Also, the installer allows for non-root installations.

I don't have root access & I would like to try out whatever features of Amplifier are usable. Is this not possible? If so, you have bugs in the documentation & the installer script.

Cita:

iliyapolak escribió:

Can you post call stack info?

Here is what I get when running amplxe-gui from gdb (I have replaced my install dir with ${INSTALL_DIR} in the output):

(gdb) run
Starting program: ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/amplxe-gui
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x2aaaaaaab000
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00002aaaac536996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
(gdb) backtrace
#0  0x00002aaaac536996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
#1  0x00002aaaac536698 in cfgmgr2::IConfigDescriptorRegistry::create(cfgmgr2::config_type_t, gen_helpers2::sptr_t<cfgmgr2::IContextValueMap const>) ()
   from ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
#2  0x00002aaab4288cea in perfclient_1_3::AnalysisTypeHolder::fill() () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/lib64/libamplxe_client_stub_1.3.so
#3  0x00002aaab42825e9 in perfclient_1_3::IdeCallback::initialize(eil1::IDE_Env*, char const*) () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/lib64/libamplxe_client_stub_1.3.so
#4  0x00002aaab4286c11 in StartUp () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/lib64/libamplxe_client_stub_1.3.so
#5  0x0000000000467480 in ?? ()
#6  0x0000000000433abc in ?? ()
#7  0x0000000000450c56 in ?? ()
#8  0x000000000045146a in wxAppConsole::CallOnInit() ()
#9  0x00002aaaab3571b4 in wxEntry(int&, char**) () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/../lib64/libwx_gtk2-2.8.so.0
#10 0x000000000044dc1b in ?? ()
#11 0x0000003822a1d994 in __libc_start_main () from /lib64/libc.so.6
#12 0x000000000041b3ea in wxHtmlHelpController::wxHtmlHelpController(int, wxWindow*) ()
#13 0x00007fffffffbb18 in ?? ()
#14 0x0000000000000000 in ?? ()

Do you have registers context?

Cita:

iliyapolak escribió:
Do you have registers context?

I'm sorry I don't know what you mean - could you explain what this is and how I get it?

Very strange.  The stack trace you provided suggests that the blow-up you saw was in some sort of configuration manager,  cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry, which to me suggests the possibility that not all went right with the install.  And I realized that I had never installed VTune as a non-root user.  So I picked up a copy of the new Update 8 and attempted to install it on a virgin system, newly installed with RHEL 6.2 (not 5.8 but close).  I had to select the non-root install option and take care to move the installation directory to a writeable place with sufficient space (which on this machine is NOT my home directory), but everything repeated smoothly and I was able to run amplxe-gui without crashing.  

So I can't really conclude much from this exercise.  I was not able to reproduce the symptoms you describe but I don't have an equivalent machine to experiment with.  The only suggestion I can offer at this point is you try to uninstall and reinstall the package.  But I do have some further questions:  Are you able to run amplxe-cl for more rigorous activities than just getting the version number?  Is it possible that your RHEL 5.8 machine is missing some basic support libraries, like Xwindows stuff (needed for amplxe-gui)?  Are there any installation logs still in /tmp that might provide clues about a failed installation?  (Should be some time-stamped files prefaced with "intel." in /tmp that might provide some clues.)

I uninstalled update 7 and downloaded & installed update 8.

During installation, I saw the following messages which may be relevant:

/tmp/install.KglE2O/li_plugin_bash.mnfXJV: line 431: ./insmod-sep3: Permission denied

and

Prerequisite(s)
-- Linux* OS kernel version is not suitable for Power analysis

Otherwise, things seemed to me to go smoothly during install. I have checked diskspace is available.

I think the machine has basic support libraries, especially when it comes to X since I run a whole bunch of graphical things on this workstation. But if you have specifics I could check, let me know.

I attach log files from the /tmp partition corresponding to the install of update 8. I notice in there that it says users should be part of vtune group, wich I haven't set up yet - but I guess that should not crash the gui. I attach the logs in case you can see something there.

I've not had a chance to test amplxe-cl yet.

Fichiers joints: 

I've seen the insmod error on recent installs but it hasn't seemed to cause me any problems, so I think it's innocuous.  The power analysis warning is just because of the age of the kernel you're running on and shouldn't lead to the behavior that you're experiencing.  The Xlib stuff I was thinking about is all pretty basic and generic, so if you're used to running apps that use X graphics, that's probably not the issue.  It still would be interesting to know whether you can use amplxe-cl to collect data despite the condition of your installation, a useful exercise to narrow the cone of suspicion.  

I didn't see anything in the files you uploaded that raised any concern.  It looks like the install was successful (though I'm no expert at reading these files).  You might also try to generate a report using amplxe-feedback (in the bin32 directory), something like:

<VTune install directory>/bin32/amplxe-feedback -create-bug-report=<your bug report name>

Upload that report and I can pass it along to the development team. Perhaps they can identify a cause from evidence I'm failing to grasp. 

The only other thing that pops into my head is licensing.  I once saw a problem in an older version of VTune Amplifier because of issues with the license files, either an inadequate one or one found in a directory among a bunch of expired licenses (details fuzzy now), which caused a crash.  But that bug should be long dead.

Hi Robert,

So I tested amplxe-cl on the Fortran sample test which comes with the distribution (nqueens_parallel). Here's what happened:

$ amplxe-cl -collect hotspots nqueens_parallel
 Usage: threading_issues.exe boardSize
 Using default size of 10
Starting nqueens solver for size 10 with 4 thread(s)
Number of solutions: 724
Correct Result!
Calculations took 4ms.
amplxe: Using result path `/scratch/alr99/130606_ampl_test/nqueens_fortran/linux/r000hs'
Intel(R) VTune(TM) Amplifier XE 2013 (build 290588) feedback tool
Copyright (C) 2009-2013 Intel Corporation. All rights reserved.

Intel(R) VTune(TM) Amplifier XE 2013 Update 8 experienced an unexpected error.

Please send a problem report:
amplxe-feedback --send-crash-report "/tmp/amplxe-log-alr99/2013-06-06-Thu-09-32-24-766441.amplxe-cl/crash_info.txt"

Report data may be used to improve product stability. Our apologies for the inconvenience and thank you for your assistance.

Exception: 0xb, Segmentation&nbsp;fault
Module: libamplxe_cfgmgr_2.15.so
Collecting system information...
Collecting modules information...
Abort

I then ran the amplxe-feedback command as suggested - the txt files are attached to this post.

I do have a bunch of expired licenses in my license directory, but at least the ifort compiler doesn't complain about anything... Do you think it's worth attempting a cleanup of my license folder?

Fichiers joints: 

It can't hurt to experiment with deleting expired licenses, though I have not seen this bug recently and so hold little hope that the solution will be that simple.  As long as you have the time (It will take a little time for me to file an internal escalation and get someone from the development team to look at this), it's one more possiblity to eliminate.

Hi:

Did you install in your $HOME dir?  Do you have $TMP defined?  Are you executing the commands in a directory that is writeable?  I know you don't want to give personal info away, but without some details it's difficult to determine what is wrong.  BTW, for secure communications with the VTune Amplifier XE support staff, you can submit your problem to Intel(R) Premier Support.

Regards, MrAnderson

Cita:

MrAnderson (Intel) escribió:

Hi:

Did you install in your $HOME dir?  Do you have $TMP defined?  Are you executing the commands in a directory that is writeable?  I know you don't want to give personal info away, but without some details it's difficult to determine what is wrong.  BTW, for secure communications with the VTune Amplifier XE support staff, you can submit your problem to Intel(R) Premier Support.

Yes, the install is under my $HOME directory.

I have $TMP defined

Yes, I'm running this in a directory that is writable.

Cita:

I know you don't want to give personal info away, but without some details it's difficult to determine what is wrong.

I have given lots of details - what more do you need?

I don't mind about the personal information. The logs I attached in previous message are full of it.

Cita:

BTW, for secure communications with the VTune Amplifier XE support staff, you can submit your problem to Intel(R) Premier Support.

Thanks. Where possible I like using the forums rather than Premier because that way the solution is shared with future visitors.

Thanks!  So, when you ran the 'amplxe-feedback -create-bug-report <name>.zip' command, it should have created a zip file with lots of files in it.  One, in particular, woudl be the qfagent<suffix>.log file.  Can you either upload the full zip file or the qfagent log file?  Thanks.

Regards, MrAnderson

Cita:

MrAnderson (Intel) escribió:

Thanks!  So, when you ran the 'amplxe-feedback -create-bug-report <name>.zip' command, it should have created a zip file with lots of files in it.  One, in particular, woudl be the qfagent<suffix>.log file.  Can you either upload the full zip file or the qfagent log file?  Thanks.

Unfortunately, here's what happens when I try to create a bug report:

$ amplxe-feedback --create-bug-report 130606_1537.zip
Intel(R) VTune(TM) Amplifier XE 2013 (build 290588) feedback tool
Copyright (C) 2009-2013 Intel Corporation. All rights reserved.
Collecting pids tree
sh: /tmp/amplxe-log-alr99/2013-06-06-Thu-15-40-51-190263.amplxe-feedback/qfagent.cmd: /usr/bin/perl^M: bad interpreter: No such file or directory

Of course, I do have perl there:

$ perl --version

This is perl, v5.8.8 built for x86_64-linux-thread-multi

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

$ which perl
/usr/bin/perl
$ ls -lh /usr/bin/perl
-rwxr-xr-x 2 root root 19K Oct 12  2012 /usr/bin/perl

I'm trying to sort this out now so I can get a log file to you. I suspect the ^M in the error message hints at some text file encoding issue, but no luck so far. Have you seen that issue before with the amplxe-feedback tool?

That reminds me, which shell are you running?  I thought I saw tcsh in one of the previous files you provided.  Can you start up bash and try commands from that shell?

Regards, MrAnderson

Cita:

MrAnderson (Intel) escribió:

That reminds me, which shell are you running?  I thought I saw tcsh in one of the previous files you provided.  Can you start up bash and try commands from that shell?

I use tcsh normally. Here is what happens when I do things under bash - as far as I can tell, exactly the same:

$ bash
bash-3.2$ source ~/intel/vtune_amplifier_xe/amplxe-vars.sh
Copyright (C) 2009-2013 Intel Corporation. All rights reserved.
Intel(R) VTune(TM) Amplifier XE 2013 (build 290588)
bash-3.2$ amplxe-cl -collect hotspots nqueens_parallel
 Usage: threading_issues.exe boardSize
 Using default size of 10
Starting nqueens solver for size 10 with 4 thread(s)
Number of solutions: 724
Correct Result!
Calculations took 30ms.
amplxe: Using result path `/scratch/alr99/130606_ampl_test/nqueens_fortran/linux/r003hs'
Intel(R) VTune(TM) Amplifier XE 2013 (build 290588) feedback tool
Copyright (C) 2009-2013 Intel Corporation. All rights reserved.

Intel(R) VTune(TM) Amplifier XE 2013 Update 8 experienced an unexpected error.

Please send a problem report:
amplxe-feedback --send-crash-report "/tmp/amplxe-log-alr99/2013-06-06-Thu-15-56-41-235633.amplxe-cl/crash_info.txt"

Report data may be used to improve product stability. Our apologies for the inconvenience and thank you for your assistance.

Exception: 0xb, Segmentation&nbsp;fault
Module: libamplxe_cfgmgr_2.15.so
Collecting system information...
Collecting modules information...
Aborted
bash-3.2$ amplxe-feedback --create-bug-report 130606_1557.zip
Intel(R) VTune(TM) Amplifier XE 2013 (build 290588) feedback tool
Copyright (C) 2009-2013 Intel Corporation. All rights reserved.
Collecting pids tree
sh: /tmp/amplxe-log-alr99/2013-06-06-Thu-15-57-17-153382.amplxe-feedback/qfagent.cmd: /usr/bin/perl^M: bad interpreter: No such file or directory

Cita:

A. Rohou escribió:

I'm trying to sort this out now so I can get a log file to you. I suspect the ^M in the error message hints at some text file encoding issue, but no luck so far. Have you seen that issue before with the amplxe-feedback tool?

I'm having no luck. It seems this .cmd file is being generated on the fly by amplxe-feedback tool, so I have no way of removing special characters from it or changing the encoding (it's encoded for DOS, not UNIX right now, which is why I think the line endings may be wrong).

Is there another way for me to get the log information to you?

EDIT: I was able to run the qfagent.cmd script manually after running it through the dos2unix utility. This means that the amplxe-feedback has a bug when running under UNIX - it generates the .cmd file with the wrong encoding.

I am trying to run this script manually now. WIll upload output in a separate post if I can get it to work.

Thanks.  No, we have never seen this issue before.  These scripts all work fine for us and we haven't had a customer report this problem.  It will be interesting to get to the root cause of your issue. :)

Regards, MrAnderson

Cita:

A. Rohou escribió:

Quote:

iliyapolak wrote:Do you have registers context?

I'm sorry I don't know what you mean - could you explain what this is and how I get it?

Sorry for late answer.Register context = values contained in gp registers during segfault.

>>>0x00002aaaac536996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
(gdb) backtrace
#0  0x00002aaaac536996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) () from ${INSTALL_DIR}/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so>>>

Can you  post value of char const* at the time of segfault? I suppose that value can point to bad memory region(unaccessible).

@A.Rohou,

do you have any updates on your problem?

Yes, I have tried to run the qfagent.cmd script manually after fixing its encoding. However, it never completes, so i cannot provide the full system information that Mr Anderson requested. Here is what I tried to do - perhaps I have the syntax wrong when calling the script?

$ /tmp/amplxe-log-alr99/2013-06-06-Thu-16-25-37-853042.amplxe-feedback/qfagent.cmd /tmp/amplxe-log-alr99/2013-06-06-Thu-16-25-37-853042.amplxe-feedback /gusr/alr99/linux/intel/vtune_amplifier_xe vtune_amplifier_xe
Quality Feedback Agent
Version: Quality Feedback Agent for Linux*
Time: Mon Jun 10 13:31:18 2013

This diagnostic script generates detailed system information about your system.
When  you forward  the output of this command to Intel(R) Support, the enclosed
server data will be used solely for the purposes of troubleshooting the problem
you have reported to Intel(R) Support. This information will not be shared with
any other companies or users, nor will it be used for any other purpose.

The script is collecting info. Please wait ...
Getting Hardware Information ...
        * Detecting architecture type
        * CPU info
        * CPU affinity
        * Amount of memory
        * PCI/AGP cards installed
Getting Software Information ...
        * Kernel version and type (UP/SMP)
        * glibc version
        * gcc version
        * icc version
        * NPTL version
        * Detecting Linux* distribution
Warning: The product has not been validated with this platform
It may work, but it is not supported
        * Checking IA32 libraries
        * File system disk space usage
        * Intel(R) Software Products installed
        * List loaded kernel modules
        * Check Linux* kernel sources availability
        * Check if sampling driver can be compiled
        * Environment variables
        * System configuration variables
        * System limits and kernel parameters
        * Permission to directories
        * Detecting GTK* and Motif* versions
        * Current locale
        * SELinux configuration
        * The list of running product processes
        * Query runlevel information for system services
        * Information on IPC facilities
        * Current user credentials
Product specific files ...
        * Product install dir
        * Product version
        * Product Driver Kit version
        * Product licenses
        * Printing bootup messages by dmesg
        * Printing messages from file /var/log/messages
        * Install log
        * Uninstall log
        * Product core files ...

At that point, the script hangs for 2+ days (I've tried this twice already).

Mr Anderson, I would like to provide you with the info you need to reproduce this - can you think of another way?

Did you try to check with GDB what I have suggested in one of my previous posts [ 06/07/2013 - 01:44]?

Today I installed the Update4 and have the same error. Ubuntu 11, Cluster Studio 2013, all recent updates.

Can you post stack trace

Sure:

NAME@NODE:/opt/intel/vtune_amplifier_xe/bin64$ gdb amplxe-gui
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 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-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /opt/intel/vtune_amplifier_xe_2013/bin64/amplxe-gui...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/intel/vtune_amplifier_xe_2013/bin64/amplxe-gui
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5f3c996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
from /opt/intel/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
(gdb) backtrace
#0 0x00007ffff5f3c996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
from /opt/intel/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
#1 0x00007ffff5f3c698 in cfgmgr2::IConfigDescriptorRegistry::create(cfgmgr2::config_type_t, gen_helpers2::sptr_t<cfgmgr2::IContextValueMap const>) ()
from /opt/intel/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
#2 0x00007fffe9504cea in perfclient_1_3::AnalysisTypeHolder::fill() () from /opt/intel/vtune_amplifier_xe_2013/lib64/libamplxe_client_stub_1.3.so
#3 0x00007fffe94fe5e9 in perfclient_1_3::IdeCallback::initialize(eil1::IDE_Env*, char const*) ()
from /opt/intel/vtune_amplifier_xe_2013/lib64/libamplxe_client_stub_1.3.so
#4 0x00007fffe9502c11 in StartUp () from /opt/intel/vtune_amplifier_xe_2013/lib64/libamplxe_client_stub_1.3.so
#5 0x0000000000467480 in ?? ()
#6 0x0000000000433abc in ?? ()
#7 0x0000000000450c56 in ?? ()
#8 0x000000000045146a in wxAppConsole::CallOnInit() ()
#9 0x00007ffff70b61b4 in wxEntry(int&, char**) () from /opt/intel/vtune_amplifier_xe_2013/bin64/../lib64/libwx_gtk2-2.8.so.0
#10 0x000000000044dc1b in ?? ()
#11 0x00007ffff3e4430d in __libc_start_main (main=0x44dbe0, argc=1, ubp_av=0x7fffffffdb18, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffdb08) at libc-start.c:226
#12 0x000000000041b3ea in ?? ()
#13 0x00007fffffffdb08 in ?? ()
#14 0x000000000000001c in ?? ()
#15 0x0000000000000001 in ?? ()
#16 0x00007fffffffdda0 in ?? ()
#17 0x0000000000000000 in ?? ()
(gdb)

 Because when I said: The same error, this implied, that the call stack was the same :)

I removed vtune amplifier completely and reinstalled Update8 -> no change

Thanks:)

This exactly the same call stack like in previous user post.

>>>0x00007ffff5f3c996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
from /opt/intel/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so
(gdb) backtrace
#0 0x00007ffff5f3c996 in cfgmgr2::ConfigDescriptorRegistry::ConfigDescriptorRegistry(cfgmgr2::config_type_t, char const*) ()
from /opt/intel/vtune_amplifier_xe_2013/bin64/../lib64/libamplxe_cfgmgr_2.15.so>>>

I suppose that this parameter  char const*  can be root cause of the problem.Can you resolve with gdb the address char pointer ?

Thanks. If you tell me how, i will try. Because I don't have really experience in Linux debugging. I normally work under Windows with Visual Studio.

Sorry Michael I also do not have much experience in Linux debugging:( I am more experienced in Windows debugging.

Maybe someone more experineced in Linux debugging can provide some help?

Michael B, are you also trying to install VTune Amplifier XE as a non-privileged user?  One person's failure is an anomaly.  Two persons' failures are a trend.  We need to understand the circumstances of these failures to try to identify the fault.  At this point it's not really clear.

Hi robert,

do you know how to resolve with GDB memory addresses?

Hi Robert. I did two attemps. First with a sudo ./install.sh and the second one with a "sudo su" and then "./install.h". So I would say I tried it two times as a -privileged user.

Cita:

Michael B. escribió:

Hi Robert. I did two attemps. First with a sudo ./install.sh and the second one with a "sudo su" and then "./install.h". So I would say I tried it two times as a -privileged user.

What was the result?

Well, it seems that there is some common defect that is causing the configuration manager in VTune Amplifier to SEGV rather than handle the anomaly in an orderly fashion.  Unfortunately, my attempts to reproduce the symptoms on one of the machines available to me have so far ended in failure (i.e., failure to reproduce a fault--the code runs without a SEGV for me).  Worse, though both A. Rohou and Michael B. report failures with similar looking stack traces, nothing shared so far offers any clue about common factors between the two cases that might explain why these failures are occurring.  Moreover, all A. Rohou's attempts were following installs as a nonpriviledged user whereas Michael B. did the installations under sudo (which presumes that he had the rights to run sudo on this machine? ;-). So the unpriviledged install I think can be removed from the symptoms list.

 And yet we're still at this impasse, where I don't have enough information to reproduce the problem locally.  And so far A Rohou's attempts to gather more details have been stymied by a seemingly similar failure.  Michael B., do you also have that problem?  Have you been able to run amplxe-feedback as described previously in this thread?  Or does it also crash for you?

The stack traces above all seem to point to the configuration manager within VTune Amplifier but don't offer much in the way of diagnostics beyond that.  What we need is more insight into the environments where these failures have occurred.  We already know something of A. Rohou's environment (Intel processors, RHEL 5.8,...).  That all seems pretty normal.  Unfortunately.  I'll contact someone on the development team and show them what we know so far--maybe it will spark some insight--but without having sufficient information to reproduce the problem, it's very hard to investigate these failures.

@robert-reed: It might be helpful to know what information your feedback tool collects from the system. I could then get this information myself and forward it to you. I can imagine that the versions of some key libraries (glib etc) and whether some kernel modules are present would be needed, but if you could give me a list of things to look for, that'd help.

@ iliyapolak : I also do not know how to use gdb to get these values and I've been too busy to teach myself how to do so.

@A.Rohou

I have found which command can be used to inspect the memory address beign pointed by pointer.I think that this command can be helpful

x/w address 
x/4b &variable 

Hi Robert,

sry I was away for a week. I will follow the steps to get informations.

We also use Intel machines (Sandybridge E26xx) on two socket boards with 128 GB RAM, running Ubuntu 11.

Update 1:

If I try the feedback tool, I get: 

Intel(R) VTune(TM) Amplifier XE 2013 (build 290588) feedback tool
Copyright (C) 2009-2013 Intel Corporation. All rights reserved.
Collecting pids tree
sh: /tmp/amplxe-log-root/2013-06-24-Mon-14-25-52-839477.amplxe-feedback/qfagent.cmd: not found

it creates a zip-file, but the *.log therein is empty.

I tried duplicating A Rohou's results when I first started looking at this thread but wasn't able to see a problem.  However, I tried to duplicate your symptoms, Michael B, with a new install of the latest update (9) and discovered that qfagent is found but fails to run for me.  I've reported it to the development team.  We should soon see a fix.  

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

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.

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

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

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.

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!

Glad that you solved installation problems.

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.

Cita:

Michael B. escribió:

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.

The keeper of the city keys Put shutters on the dreams. I wait outside the pilgrim's door With insufficient schemes. The black queen chants The funeral march, The cracked brass bells will ring; To summon back the fire witch To the court of the crimson king.

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

 

Pages

Connectez-vous pour laisser un commentaire.