> root$valgrind --tool=callgrind ./basic > out.txt
It is *always* a bad idea to run an application as root
unless the app requires elevated privileges. DO NOT run valgrind as root.
Create and run as a real non-root user; consult your system documentation.
<<snip>>
> ==2405== For interactive control, run 'callgrind_control -h'.
> --2405-- WARNING: Serious error when reading debug info
> --2405-- When reading debug info from
> /opt/valgrind/lib/valgrind/callgrind-arm-linux:
> --2405-- Missing or invalid ELF Section Header Table
Check if you get the same or similar message when running something other than
callgrind.
Try --tool=none or --tool=memcheck .
Inspect the file /opt/valgrind/lib/valgrind/callgrind-arm-linux .
It should be a copy of some callgrind-x86-linux located within the build
directory.
(It is common to run out of disk space on a machine where you are tempted
to run apps as the root user.)
What does the 'file' utility program say about callgrind-arm-linux?
Does "readelf --sections" give good output?
Compare /opt/valgrind/lib/valgrind/callgrind-arm-linux with callgrind-i686-linux
(because you say that it works on x86 ubutntu.) Obviously the exact contents
differ,
but other characteristics (size, owner, date, permissions, ...) should be
similar.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
