Yes I do. I think this might be a debug-file-directory setting issue. The app and one of the libs it's using are in /usr/local/ the debug for libc is in /usr/. Not sure you can have multiple directories in .gdbinit for debug-file-directory. Least it seems to be ignoring it.
Figure I'll trying copying the debug libs all over into one place and see what that does. Failing that. Upgrade time.
On Tue, Jun 17, 2014 at 8:33 AM, Siarhei Siamashka siarhei.siamashka@gmail.com wrote:
On Tue, 17 Jun 2014 08:17:26 -0500 Tom Gall tom.gall@linaro.org wrote:
On Tue, Jun 17, 2014 at 2:35 AM, Will Newton will.newton@linaro.org wrote:
On 13 June 2014 18:14, Tom Gall tom.gall@linaro.org wrote:
Hi Tom,
I'm trying to use valgrind on an a15, 32 hf environment obviously.
I have -g on with no optimization for all my code that is being run.
Command line options for valgrind are:
valgrind -v --tool=memcheck --leak-check=full --show-reachable=yes --leak-resolution=high --track-origins=yes --num-callers=10 ./matvec
I tried this command line on Ubuntu Trusty and got complete looking call stacks.
I'm on 12.04 precise.
Bummer.
Do you have something like libc-dbg installed in your system? Having the glibc debugging symbols is important.
-- Best regards, Siarhei Siamashka