Vtune 3.0 on Fedora core 1

[Intel_C_Intel]

I've installed vtune on fedora core 1 (in the package there is the kernel module for this distribution).

When I try it on a test application I get the following:

------------------------------------

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

The Activity is running.
Tue Dec 14 13:18:55 2004 Reading property files started...

Tue Dec 14 13:18:55 2004 Reading property files done.

Tue Dec 14 13:18:56 2004 Static instrumentation started
Tue Dec 14 13:18:57 2004 All functions instrumentation of module "appexe" was successful.
Tue Dec 14 13:19:00 2004 Exports instrumentation of module "libatk-1.0.so.0.400.0" was successful.
Tue Dec 14 13:19:04 2004 Exports instrumentation of module "libc-2.3.2.so" was successful.
Tue Dec 14 13:19:04 2004 All functions instrumentation of module "libcrypt-2.3.2.so" was successful.
Tue Dec 14 13:19:04 2004 Minimal instrumentation of module "libdl-2.3.2.so" was successful.
Tue Dec 14 13:19:04 2004 Exports instrumentation of module "libexpat.so.0.4.0" was successful.
Tue Dec 14 13:19:04 2004 Exports instrumentation of module "libfontconfig.so.1.0.4" was successful.
Tue Dec 14 13:19:05 2004 Exports instrumentation of module "libfreetype.so.6.3.3" was successful.
Tue Dec 14 13:19:05 2004 Exports instrumentation of module "libgdk-x11-2.0.so.0.200.4" was successful.
Tue Dec 14 13:19:05 2004 Exports instrumentation of module "libgdk_pixbuf-2.0.so.0.200.4" was successful.
Tue Dec 14 13:19:06 2004 Exports instrumentation of module "libglib-2.0.so.0.200.3" was successful.
Tue Dec 14 13:19:06 2004 Exports instrumentation of module "libgmodule-2.0.so.0.200.3" was successful.
Tue Dec 14 13:19:06 2004 Exports instrumentation of module "libgobject-2.0.so.0.200.3" was successful.
Tue Dec 14 13:19:10 2004 Exports instrumentation of module "libgtk-x11-2.0.so.0.200.4" was successful.
Tue Dec 14 13:19:10 2004 Exports instrumentation of module "libguile-ltdl.so.1.0.0" was successful.
Tue Dec 14 13:19:10 2004 Exports instrumentation of module "libguile.so.12.3.0" was successful.
Tue Dec 14 13:19:10 2004 All functions instrumentation of module "libm-2.3.2.so" was successful.
Tue Dec 14 13:19:11 2004 Exports instrumentation of module "libpango-1.0.so.0.200.5" was successful.
Tue Dec 14 13:19:11 2004 Exports instrumentation of module "libpangox-1.0.so.0.200.5" was successful.
Tue Dec 14 13:19:11 2004 Exports instrumentation of module "libpangoxft-1.0.so.0.200.5" was successful.
Tue Dec 14 13:19:11 2004 Exports instrumentation of module "libpthread-0.60.so" was successful.
Tue Dec 14 13:19:12 2004 Exports instrumentation of module "libqthreads.so.12.3.0" was successful.
Tue Dec 14 13:19:12 2004 Exports instrumentation of module "libX11.so.6.2" was successful.
Tue Dec 14 13:19:12 2004 Exports instrumentation of module "libXext.so.6.4" was successful.
Tue Dec 14 13:19:12 2004 Exports instrumentation of module "libXft.so.2.1.1" was successful.
Tue Dec 14 13:19:13 2004 Exports instrumentation of module "libXi.so.6.0" was successful.
Tue Dec 14 13:19:13 2004 Exports instrumentation of module "libXrandr.so.2.0" was successful.
Tue Dec 14 13:19:13 2004 Exports instrumentation of module "libXrender.so.1.2.2" was successful.
Tue Dec 14 13:19:13 2004 Exports instrumentation of module "libz.so.1.2.0.7" was successful.
Tue Dec 14 13:19:13 2004 St atic instrumentation done
Tue Dec 14 13:19:18 2004 Data collection finished...
Tue Dec 14 13:19:18 2004 No module from the activity was loaded
Tue Dec 14 13:19:18 2004 Error in module "" - Internal error while resolving the results file..
The Activity has finished running.

-----------------------

The commandline is: vtl activity -c callgraph -app appexe -moi appexe run

How can I solve this?

[jeffrey-gallagher]

Hey LG, nice to see you posting here. Two quickies:

1) what kernel is installed?

2) are there any reported failures in your install.log, default location:

/var/og/install.log

(You might have to vi the install.log and examine it quickly line by line -< there's a date and time stamp, and then either a "Success" or a "Failed." The FAILED lines are the ones we should know about.

cheers

jdg

[Intel_C_Intel]

The kernel installed is:
kernel-smp-2.4.22-1.2115.nptl

I had the newer version but I come back to this because of Vtune, infact in the package there is a compiled module for this version of the kernel.'

In the log there are some fails about some rpm installs, here is an example:
-----------------------------------------
mar 12 12:19:29: Success - Package search: 'intel-vtune-shell_cli-3.0b-620.x32.rpm' => 'NAME' => 'intel-vtune-shell_cli'
mar 12 12:19:29: Success - Create temp '/tmp/temp.arz8743' in '/tmp'.
mar 12 12:19:29: Success - Using rpm install without relocation.
mar 12 12:19:29: Success - 'intel-vtune-shell_cli-3.0b-620.x32.rpm' installed
mar 12 12:19:30: Failed - Package 'intel-vtune-ism_cli' not found
mar 12 12:19:30: Success - Install rpm - intel-vtune-ism_cli-3.0b-597.x32.rpm
mar 12 12:19:30: Success - Options are: ''.
mar 12 12:19:30: Success - Using file query for package - 'intel-vtune-ism_cli-3.0b-597.x32.rpm'
-----------------------------------------

but if I perform
rpm -qa | grep intel
all the rpms are installed:

]# rpm -qa | grep intel
intel-icc_ide8-8.1-023
intel-vtune-shared_cli-3.0b-597
intel-vtune-entirex_dummy-3.0b-620
intel-isubh8-8.1-023
intel-vtune-standaloneviewers-3.0b-620
intel-icc8-8.1-023
intel-vtune-shell_core-3.0b-620
intel-vtune-ism_cli-3.0b-597
intel-vtune-analyzer_cli-3.0b-620
intel-iidb8-8.1-036
intel-vtune-runtimelibs-3.0b-620
intel-vdk-3.2-32
intel-vtune-shell_cli-3.0b-620
intel-vtune-lips_cli-3.0b-620
intel-vtune-vdk_dummy-3.0b-620
intel-vtune-cpluspluslibs-3.0b-620
intel-vdk-src-3.2-32
intel-vtune-bistro_cli-3.0b-620
intel-vtune-shell_gui-3.0b-620
intel-vtune-analyzer_gui-3.0b-620


During install process, I've had to run the custom installation because the installer says fedora core 1 isn't supported (even if there is the precompiled kernel module in the package).

[jeffrey-gallagher]

OK. I was assuming your setup was like this:

--- Fedora core 1 system running vtserver, the linux remote agent

--- you're running the vtl 3.0 itself on a supported RH or SuSE system

--- you launch the activity from vtl, the collection is managed by vtserver, and the results are sent back to vtl

I'm getting the impression now that this is not your setup. Can you confirm one way or the other?

cheers

jdg

[Intel_C_Intel]

I'm running vtl 3.0 on fedora core 1 without vtserver.
I suppose fedora core 1 isn't supported, even if in the package(downloaded from intel website) there is the kernel module (the driver) compiled for fedora core 1.

Is there something wrong in this configuration? Should I install vtserver even if I use it on the same system?

[David_A_Intel1]

So, a couple of thoughts. First, the driver you refer to is the sampling driver and has nothing to do with call graph. Have you attempted to collect sampling data? This will probably work.

Second, since call graph's remote counter part is no less demanding than the local version, using a remote setup, as was suggested, will probably not help.

Have you tried collecting this data using the Eclipse-based GUI (invoke 'vtlec')? If it fails there, you can try lowering the instrumention levels on all files and re-running. If at the "Minimal" setting, the application works, then you can start increasing the instrumentation level, module by module, until you either collect the data you want or find the module that doesn't like to be instrumented. (Note: you can also do this from the command line, by setting the appropriate 'global-options'; see the help.)

Finally, note these limitations from the release notes (/opt/intel/vtune/VTLRELEASENOTES.htm; you may want to check out the rest):

• If you are upgrading your version of the VTune analyzer, after installation you may discover it is not possible to create a Call graph project. To correct this issue, remove the /tmp/vtune_username/ directory, which ensures that the files in it were not created by an older version of the VTune analyzer.
• Call Graph adds the pthreads library to the instrumented application in order to profile it. Call graph profiling does not support applications that can not link to the pthread library into the executable.