|
From: Josef W. <Jos...@gm...> - 2005-07-12 19:44:15
|
Hi Justace, I really do not know why valgrind does not read in debug info from treffytng on your system. On mine this is working. I am simply missing a line saying ==6874== Reading syms from /home/weidendo/tmp/vgbug/treffytng (0x8048000) in valgrinds output (because of verbose "-v"). What happens if you start the binary via absolute path, e.g. valgrind -v --tool=none /path/treffytng You could also check with strace -eopen valgrind treffytng if there is any suspicious line failing to open the binary for debug reading. Someone other on the list has any idea? On Tuesday 12 July 2005 15:29, you wrote: > Could this be a problem of how our valgrinds are compiled? Did you compile valgrind in any special way? > Or the version of GCC on our computers. I am using 3.4.4 which from > what I understand is a relatively new version. Your binary seems running quite fine with my valgrind installation, so the compiler does not seem to be the problem. It must have to do something with the setup of your computer, but I have no idea, sorry. Josef |