Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
4995 Discussions

Unknown function Name???

jvong
Beginner
393 Views
Hi all,
I am new to VTune and have a question in viewing the data.
I tried to look into the function view of a callgraph activity.
However, the view did not show the function name, but all fuction name are "unknown".
My question is,under whatsituation will make thefunction nameunknown? And is there any solution to this?
I wanted to optimise the code but it is impossible if I dont even know what function is most consuming.
I have already compile the program with gcc with -g options. And the following is the first few lines of the functions view output.
[NAME(1)]; [MODULE(2)]; [THREAD(3)]; [CLASS(4)]; [SELF_TIME(5)]; [TOTAL_TIME(6)]; [WAIT_TIME(7)]; [TOTAL_WAIT_TIME(8)]; [#_CALLS(9)]; [#_CALLERS(10)]; [#_CALLEES(11)]; [ADDRESS(12)]; [MANGLED_NAME(13)]; [DISPLAY_NAME(14)]; [PROCESS(15)]; [SOURCE_FILE(16)]; [PID(17)]
Thread_2000; unknown; Thread_2000; ; 71414376; 71414376; 0; 0; 1; 0; 4; 0x0; unknown; unknown; /usr/local/bin/clamdscan; unknown; 9685
unknown; /usr/local/bin/clamdscan; Thread_2000; ; 25; 71414371; 0; 0; 1; 1; 5; 0x3BD0; ; ; /usr/local/bin/clamdscan; unknown; 9685
unknown; /usr/local/bin/clamdscan; Thread_2000; ; 644; 71414320; 0; 0; 1; 1; 25; 0x2230; ; ; /usr/local/bin/clamdscan; unknown; 9685
unknown; /lib/libc.so.6.1; Thread_2000; ; 1363; 71404596; 0; 0; 279; 2; 5; 0xD6C20; ; ; /usr/local/bin/clamdscan; unknown; 9685
unknown; /lib/libc.so.6.1; Thread_2000; ; 465; 71402499; 0; 0; 279; 1; 1; 0xD8C10; ; ; /usr/local/bin/clamdscan; unknown; 9685
All help is appreciated.
Seve

Message Edited by jvong@mailprove.com on 04-30-2004 12:54 AM

0 Kudos
1 Reply
jeffrey-gallagher
393 Views
Hey Seve,
An easy reason for function names not appearing is that vtl can't find the source file for the application you're looking at.
Double check your $PATH and make sure the source file directory is in there.
# echo $PATH
If the directory isn't in there, add it (like, for Bourne shell):
# PATH=$PATH:/mydirectory/mysubdir_to_sourcefile:
# export PATH
cheers
jdg
0 Kudos
Reply