IDB: Problems reading symbolic informtation from exec

IDB: Problems reading symbolic informtation from exec

hanswb's picture


Hello,
we are using IBM/Atria's ClearCase as Code Management System.
ClearCase provides a virtual file system. I compiled and linked an executable
and want to debug with idb. The executable is located in, e.g.
/project/artemis/task/test/Linux_i686_2.6.9-5.ELsmp_ifort_gcc_debug
That's the path in the virtual file system.
So ll and pwd gives:
.../test/Linux_i686_2.6.9-5.ELsmp_ifort_gcc_debug $ pwd
/project/artemis/task/test/Linux_i686_2.6.9-5.ELsmp_ifort_gcc_debug
ll
insgesamt 9421
-rwxrwx--- 1 bolloni btmc 9109683 2005-08-15 18:18 artemis_exe

But when I start idb with 'idb -gui artemis_exe', the debugger can't read the symbolic information on one host (c4i4n15):
object file name: artemis_exe
Reading symbolic information from /lib/ld-2.3.4.so...No debugging symbols found

On another host (c4i4n01), when setting the same view, the debugger finds the symbolic information:
object file name: artemis_exe
Reading symbolic information from /work_local/vstore/bolloni_artemis_0.05/.s/00018/80000bd742fcaca1artemis_exe...done


Both times, its the same executable,accessed via the virtual file system, but from different hosts. The "real" executable is located in
/nfs/c4i4n01/work_local/vstore/bolloni_artemis_0.05/.s/00018/80000bd742fcaca1artemis_exe
I guess that's the reason, idb can read the info on host c4i4n01.

My questions:
How does idb determine from which path/exec to read the symbolic info ?
idb seems to achieve and use the absolute path of the executable. Why ?
Can you offer any help, hints or suggestions ?

Thanks,
Hans

P.S.: We have
Intel Fortran Compiler for 32-bit applications, Version 9.0 Build 20050722Z Package ID: l_fc_c_9.0.025
Linux Application Debugger for 32-bit applications, Version 9.0-11, Build 20050617

on Red Hat EL4 and SuSE Enterprise

1 post / 0 new
For more complete information about compiler optimizations, see our Optimization Notice.