|
From: Tom H. <to...@co...> - 2010-10-04 13:37:13
|
On 04/10/10 14:02, adnan iqbal wrote: > Valgrinding of any dynamically linked program starts with the > valgrinding of linker. this also results in loading (via > sys_open/sys_read OR mmapping) several shared objects (e.g., > ld.so.cache and libc-2.9.so <http://libc-2.9.so>). > I am trying to figure out from where the path of these shared objects is > obtained/controlled. For example in x86-linux the path used for > libc-2.9.so <http://libc-2.9.so> is /lib/tls/i686/cmov/libc-2.9.so > <http://libc-2.9.so>. I need to do so because it appears that for other > ports of valgrind it shall be necessary to replace these paths with more > appropriate ones. This is nothing to do with valgrind - valgrind just runs ld.so in the same way the kernel normally does and ld.so decides what other shared libraries are needed and where to load then from. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |