VTL3.0 and IFC 8.1 issues

[guillermo_marcus]

Hi all,

I am using a Scientific Linux 3.0.3 linux box with kernel 2.4.21-20.EL.cernsmp (this distribution is highly based on RHEL3), with a Intel Xeon 2.66GHz and 1GB of RAM.

I am using the VTune 3.0 Beta build 620, and I configure it via the graphical interface to do a Callgraph profiling of a FORTRAN program, compiled with the Intel Fortran Compiler 8.1, build 023.

When executing, I get the following errors:

---
Tue Dec 14 20:20:28 2004 Reading property files started...

Tue Dec 14 20:20:28 2004 Reading property files failed.

Tue Dec 14 20:20:29 2004 Error in module "libcxa.so.5" - Module was not found or is not an ELF image.
Tue Dec 14 20:20:29 2004 Error in module "libunwind.so.5" - Module was not found or is not an ELF image.
Tue Dec 14 20:20:29 2004 Data collection halted...
Tue Dec 14 20:20:29 2004 No module from the activity was loaded
---

Of course, the program executes fine from the command line. I have seen the same problem previously from the command line, when the LD_LIBRARY_PATH was not pointing to the libraries directory of the IFC. I solved this by adding the following lines to the .bashrc of the user:

---
# Environment variables for Intel Debugger
source /opt/intel/idb/bin/idbvars.sh

# Environment variables for Intel Fortran Compiler
source /opt/intel/fc/bin/ifortvars.sh
---

but it seems this is not seen by the VTune graphical environment. Therefore, I tryed modifying the environment variables manually in Activity Configuration -> Application Configure... -> Advanced, but got the same result.

Then I tryed to profile it from the command line interface, with the following command:

vtl activity test-vine -d 120 -c callgraph -app [path-to-app]/[app-exe],,[path-to-app] -moi [path-to-app]/[app-exe]

produces the following output:

---
VTune Performance Analyzer 3.0 for Linux*
Copyright (C) 2000-2004 Intel Corporation. All rights reserved.

The Activity is running.
Tue Dec 14 19:36:35 2004 Reading property files started...

Tue Dec 14 19:36:35 2004 Reading property files done.

Tue Dec 14 19:36:36 2004 Static instrumentation started
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
[app-exe] 0819F21B Unknown Unknown Unknown
[app-exe] 0803BE28 Unknown Unknown Unknown
[app-exe] 0803BF3B Unknown Unknown Unknown
[app-exe] 0803A704 Unknown Unknown Unknown
[app-exe] 080394F8 Unknown Unknown Unknown
libc.so.6 0011F168 Unknown Unknown Unknown
Tue Dec 14 19:36:40 2004 All functions instrumentation of module "[app-exe]" was successful.
Tue Dec 14 19:36:41 2004 Exports instrumentation of module "libc-2.3.2.so" was skipped.
Tue Dec 14 19:36:41 2004 All functions instrumentation of module "libcxa.so.5" was successful.
Tue Dec 14 19:36:41 2004 Minimal instrumentation of module "libdl-2.3.2.so" was skipped.
Tue Dec 14 19:36:41 2004 All functions instrumentation of module "libm-2.3.2.so" was skipped.
Tue Dec 14 19:36:41 2004 All functions instrumentation of module "libunwind.so.5" was successful.
Tue Dec 14 19:36:41 2004 Static instrumentat ion done
Tue Dec 14 19:36:41 2004 Data collection started...
Tue Dec 14 19:36:42 2004 Process Call Graph (MT) Data Collection, id "23388", started writing Call Graph data.

Tue Dec 14 19:36:42 2004 Process Call Graph (MT) Data Collection, id "23388", finished writing Call Graph data.

Tue Dec 14 19:36:48 2004 Data collection finished...
Tue Dec 14 19:36:49 2004 Updating call graph database...
Tue Dec 14 19:36:49 2004 Trying to find symbols for module (1 / 5) /lib/tls/libc.so.6
Tue Dec 14 19:36:49 2004 Succeeded!
Tue Dec 14 19:36:49 2004 Trying to find symbols for module (2 / 5) /lib/libdl.so.2
Tue Dec 14 19:36:49 2004 Succeeded!
Tue Dec 14 19:36:49 2004 Trying to find symbols for module (3 / 5) /lib/tls/libpthread-0.60.so
Tue Dec 14 19:36:49 2004 Succeeded!
Tue Dec 14 19:36:49 2004 Trying to find symbols for module (4 / 5) /opt/intel/fc/lib/libunwind.so.5
Tue Dec 14 19:36:49 2004 Succeeded!
Tue Dec 14 19:36:49 2004 Trying to find symbols for module (5 / 5) [path-to-app]/[app-exe]
Tue Dec 14 19:36:49 2004 Succeeded!
Tue Dec 14 19:36:49 2004 Done.
The Activity has finished running.
---

I can perform a Sampling profile over the same executable without a problem.

I tryed also linking the Fortran libraries statically, then I got from the callgraph profile the same error as the command line version (but only after redirecting the output to a file, NOT in the console). When redirecting the outputs to a file (adding >&out.txt to the command line arguments), they go to the ~/workspace/[project-name]/.vtproject.data directory instead of to the specified working directory.

Therefore I see various issues from this tests:

The working directory for the application seems not to being changed as requested.

The environment variables for the UUT seems not to being changed as requested.

The output is not shown in the console window.

The SIGSEGV seems to be a bug in the Callgraph collector.

I couldn't post this as an issue in the Premier site as this is a Beta product release.

Cheers,
GM.

[jeffrey-gallagher]

Hey GM,

Let's see if anybody out there has duplicated an experiment Scientific Linux 3.0.3. Anybody out there try the same thing as GM?

If its imperative that you get some profiling data, then I'd suggest installing the 3.0 FCS product on a fully supported RH or SuSE OS, and, profiling the Scientific Linux application via vtserver, the linux remote agent.

cheers

jdg

[guillermo_marcus]

Hi,

I am using now the VTL 3.0 release. now if I link the libraries statically with the IFC '-static-libcxa' option it works, but it is still giving the errors:

Sat Jan 8 14:20:18 2005 Error in module "libcxa.so.5" - Module was not found or is not an ELF image.
Sat Jan 8 14:20:18 2005 Error in module "libunwind.so.5" - Module was not found or is not an ELF image.

if I try to use them dynamically linked. This seems to point more in the direction that the environment from which VTL is running the profiled program is not properly set.

Cheers,
GM

[TimP]

Yes, it does look like LD_LIBRARY_PATH is not set within the Vtune environment, to show where those libraries should be found. It ought to be inherited from the shell where you start Vtune. If not, you could make a script which sets necessary environment variables and runs your application, and run that script from Vtune. Maybe I shouldn't say it, but I often put in symlinks so that libunwind.so will be visible in /usr/lib.