No module from the activity was loaded, Error - VTune for linux
I'm a new user of VTune for Linux even though i have used VTune on Windows.
Unfortunately when i try the graphical version of vtune with eclipse embbeded IDE using vtlec to generate the call-graph for a proprietary application, i see the error message "No module from the activity was loaded, Error - Internal error while resolving the results file"
Please let me know where i could begoing wrong.
Sun Jan 30 17:51:04 2005 Reading property files started...
Sun Jan 30 17:51:04 2005 Reading property files done.
Sun Jan 30 17:51:05 2005 Static instrumentation started
Sun Jan 30 17:51:05 2005 All functions instrumentation of module "EOTMarketMonitor" was skipped.
Sun Jan 30 17:51:06 2005 Exports instrumentation of module "libc-2.3.2.so" was skipped.
Sun Jan 30 17:51:06 2005 All functions instrumentation of module "libdbt6012dg.so" was skipped.
Sun Jan 30 17:51:06 2005 All functions instrumentation of module "libdbtol.1.64.so" was skipped.
Sun Jan 30 17:51:08 2005 Static instrumentation done
Sun Jan 30 17:51:16 2005 Data collection finished...
Sun Jan 30 17:51:16 2005 No module from the activity was loaded
Sun Jan 30 17:51:16 2005 Error - Internal error while resolving the results file.
I have tried the command line Vtune using vtl commands also. When i do "ps -fu " i see that the process is running with the same name as i started. But, I'm curious to know if vtune changes the exectable name during run-time or laterbecause even though the application starts up fine and seems to be running but duringits termination, it complains that the application is unable to read some of the configuration parameters from config file. I'm puzzled why the process runs fine but complains about the configs towards the process termination when the configs are read/processed during process start up.
Hmmm. Let's start smaller to see if the installation is ok. Try running a sampling session on /bin/ls, and then a callgraph session on /bin/ls, and let's see if the same failure occurs or not. If not, we might try a small test case, with a small binary before trying your original test code.
Also, if there were any installation issues, they may be listed in the installation log, default:
It might be worth looking through there, for "FAILS" instead of passes, to see if something in the installation when awry.