On 04/07/2014 02:47 PM, Vijay Viswanathan wrote: > > I ran myprogram using : > > G_SLICE=always-malloc valgrind -v --run-libc-freeres=no --vgdb=no > --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=50 > --workaround-gcc296-bugs=yes --log-f > ile=vgdump > > I got this output : > > mypgrogram:64: can't map '/etc/ld.so.cache' > > > Any idea whats goin on?
There would be more ideas, and sooner, if you told us which hardware architecture, and which libc, and which OS, and the version number of each piece of software. It really DOES matter! Also, you should run under strace, or "valgrind --trace-syscalls=yes", to learn exactly why ld.so.cache could not be mapped. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
