|
From: Tom H. <to...@co...> - 2006-10-10 11:55:07
|
In message <520...@BA...>
Rakesh S. Shevde <Rak...@ge...> wrote:
>
> One other thing I found out is
> The exec of interest is loading a different set of vgp*.so
> --2983-- Linux version 2.6.15-2.4 (root@alfred) (gcc version 4.0.2
> 20051125 (Red Hat 4.0.2-8)) #1 SMP Fri May 26 09:51:20 CDT 2006
> --2983-- Reading syms from /usr/sbin/dpserver (0x400000)
> --2983-- Reading syms from /lib64/ld-2.3.6.so (0x11900000)
> --2983-- Reading suppressions file: /usr/lib64/valgrind/default.supp
> ==2983==
> --2983-- Reading syms from /usr/lib64/valgrind/vg_preload_core.so
> (0x11A1C000)
> --2983-- object doesn't have a symbol table
> --2983-- Reading syms from /usr/lib64/valgrind/vgpreload_memcheck.so
> (0x11B1E000)
> --2983-- object doesn't have a symbol table
>
> And I wrote a small test prog using setpriority() which is loading a
> different vgp*.so files
> --10565-- Linux version 2.6.15-2.4 (root@alfred) (gcc version 4.0.2
> 20051125 (Red Hat 4.0.2-8)) #1 SMP Fri May 26 09:51:20 CDT 2006
> --10565-- Arch and hwcaps: AMD64, amd64-sse2
> --10565-- Valgrind library directory: /usr/local/lib/valgrind
> --10565-- Reading syms from /home/sdc/rakesh/a.out (0x400000)
> --10565-- Reading syms from /usr/local/lib/valgrind/amd64-linux/memcheck
> (0x38000000)
> --10565-- object doesn't have a dynamic symbol table
> --10565-- Reading syms from /lib64/ld-2.3.6.so (0x3C1EB00000)
> --10565-- Reading suppressions file:
> /usr/local/lib/valgrind/default.supp
> --10565-- Reading syms from
> /usr/local/lib/valgrind/amd64-linux/vgpreload_core.so (0x4802000)
> --10565-- Reading syms from
> /usr/local/lib/valgrind/amd64-linux/vgpreload_memcheck.so (0x4903000)
>
> Would that give some clue, on this issue.
Yes - you have two copies of valgrind installed, one in /usr and one
in /usr/local and you have picked up different versions on different
runs, presumably due to a different path.
The one in /usr/local is newer that the one in /usr.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|