|
From: Anuta M. <man...@gm...> - 2016-02-23 05:02:48
|
Hi, I think I've found the problem. This is my output when I run the above commands: *anuta@anuta-ubuntu:/valgrind/valgrind-3.11.0$ nm inst/lib/valgrind/vgpreload_helgrind-amd64-linux.so|grep -i pthreadZucreate000000000000b84f T _vgw00000ZZ_libpthreadZdsoZd0_pthreadZucreateZAZaanuta@anuta-ubuntu:/valgrind/valgrind-3.11.0$ nm inst/lib/valgrind/vgpreload_tracker-amd64-linux.so|grep -i pthreadZucreatenm: 'inst/lib/valgrind/vgpreload_tracker-amd64-linux.so': No such file* My tool's preload file isn't in the inst/lib/valgrind directory at all. How do I fix this? My Makefile is exactly the same as Helgrind's, and I ran autogen, configure, make and make install as well. On Tue, Feb 23, 2016 at 4:11 AM, Philippe Waroquiers < phi...@sk...> wrote: > On Mon, 2016-02-22 at 14:52 +0530, Anuta Mukherjee wrote: > > Hello Anuta, > > > When I try to run it, this is the error I'm getting: > > > > > > valgrind: m_redir.c:627 (vgPlain_redir_notify_new_DebugInfo): > Assertion 'is_plausible_guest_addr(sym_avmas.main)' failed. > > Segmentation fault (core dumped) > > > > One possible reason for the above is if the wrapping code is linked to > the tool, > rather than being in the tool preload file. > > So, what you could do is (assuming you are on amd64, and that your > install is in the directory Inst): > nm Inst/lib/valgrind/vgpreload_helgrind-amd64-linux.so|grep -i > pthreadZucreate > and the same command for your tool: > nm Inst/lib/valgrind/vgpreload_tracker-amd64-linux.so|grep -i > pthreadZucreate > > Both commands should output a line such as: > 000000000000c0bc T _vgw00000ZZ_libpthreadZdsoZd0_pthreadZucreateZAZa > > If the above is ok, then run with -v -v -v -d -d -d > The tracing should show something like: > --2338:2: initimg preload_string: > following by a line containing a.o. the aboslute path name of the > tracker preload .so. > > If all the above is correct, then I have no idea. > > Maybe compare a run of your tool and helgrind > with the options > -v -v -v -d -d -d --trace-redir=yes > > The traces/differences might explain the problem. > > Philippe > > > > -- Anuta Mukherjee, Dept of Computer Science Engg, CEG, Anna University |