Hi Dave, > Also, although your main application clearly has debug information, your > target file system's libraries may not. Make sure that you have debuginfo > files in /usr/lib/.debug (default) or /usr/lib/debug. I'm not sure how > valgrind intercepts the malloc/free calls, but I assume that valgrind will > have a terrible time backtracing without dwarf info, at least on some flavors > of arm.
Thanks for reply and bringing me on the right path ! Still not understanding much, but the "solution" actually for me is to install debug symbol for valgrind itself, just for the vgpreload_memcheck-arm-linux.so lib. Installing the debug symbol for the C lib didn't change anything Cheers David ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
