Valgrind does not report any mistake. However, using valgrind -v:
--9198-- Valgrind library directory: /usr/lib/valgrind
--9198-- Reading syms from /lib/ld-2.9.so (0x4000000)
--9198-- Reading debug info from /lib/ld-2.9.so ..
--9198-- .. CRC mismatch (computed 049232cc wanted 022486d8)
--9198-- object doesn't have a symbol table
--9198-- Reading syms from /home/gcordoba/tmp/a.out (0x8048000)
--9198-- Reading syms from /usr/lib/valgrind/x86-linux/memcheck (0x38000000)
--9198-- object doesn't have a dynamic symbol table
Is this due to the same bug? It is related with a bug on the libraries?
Please. note that the "syscal write" problem which appear on any mpi related program does not appear in this case.
I just tried a very simple one line program found on an ubuntu forum (http:// ubuntuforums. org/showthread. php?t=80182):
int main(){return 42;}
Valgrind does not report any mistake. However, using valgrind -v: tmp/a.out (0x8048000) valgrind/ x86-linux/ memcheck (0x38000000)
--9198-- Valgrind library directory: /usr/lib/valgrind
--9198-- Reading syms from /lib/ld-2.9.so (0x4000000)
--9198-- Reading debug info from /lib/ld-2.9.so ..
--9198-- .. CRC mismatch (computed 049232cc wanted 022486d8)
--9198-- object doesn't have a symbol table
--9198-- Reading syms from /home/gcordoba/
--9198-- Reading syms from /usr/lib/
--9198-- object doesn't have a dynamic symbol table
Is this due to the same bug? It is related with a bug on the libraries?
Please. note that the "syscal write" problem which appear on any mpi related program does not appear in this case.