> Valgrind's VDSO collides with my executables load section. Is it possible to > relocate load VDSO ?
[vdso] was put there by the kernel during the execve() which created the current address-space layout, before valgrind itself executes any instruction. If you don't like [vdso] there, then you should adjust /proc/sys/vm/legacy_va_layout . (Still, valgrind's address-space manager should handle the collision better.) > > Below are my executables phdr details. You left out the most important part, which is whether the file is ET_EXEC or ET_DYN: $ readelf --file-header ./my_app | grep Type: > Program Headers: > * LOAD 0x000000 0x00048000 0x00048000 0xe6aff14 0xe6aff14 R E > 0x1000* The VirtAddr of PT_LOAD for an ET_DYN module is relocatable by sliding the whole module. The VirtAddr of PT_LOAD for an ET_EXEC module must not be changed. -- ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
