一、Cross-Compile/交叉编译
（1）下载及解压Valgrind-3.11
（2）修改confirure
将armv7*)修改为armv7*|arm*)
（3）执行configure
./configure CC=arm-linux-gcc CPP=arm-linux-cpp CXX=arm-linux-g++ --host=arm-linux --prefix=/opt/valgrind/lib
注意：CC=arm-linux-gcc，之所以没有像有些博客上写的、用了绝对路径，是因为「我已经将arm-linux-gcc 软链接/soft-linke 到了实际的gcc」。
（4）make
（5）make install
二、移植到ARM开发板
注意：make install之后，编译生成的bin/和lib/目录存放在PC上的/opt/valgrind/lib目录下。将此目录下的bin/和lib/目录单独「复制/Copy」出来，不要Copy share/和include/目录，因为文件有点大，而且include/和share/这两个目录在开发板上没有用。
在ARM开发板上建立「目录-/opt/valgrind/lib/valgrind/」，将上面刚刚编译得到的lib/目录下的文件（.so, .a 等）放到左边提到的这个目录（/opt/valgrind/lib/valgrind）中。
注意：上面这个步骤非常关键，如果放错位置，在运行程序valgrind的时候，会提示「failed to start 'memcheck' : No such file or directory」。
三、ARM上配置使用
1、Error：在运行「./valgrind ls」的时候依然碰到了一个错误，出现在「vgdb」。错误提示是：
[::]root@freescale ~/valgrind/valgrind/bin$ ./valgrind ls
[::]==== Memcheck, a memory error detector
[::]==== Copyright (C) -, and GNU GPL'd, by Julian Seward et al.
[::]==== Using Valgrind-3.11. and LibVEX; rerun with -h for copyright info
[::]==== Command: ls
[::]====
[::]==== error writing bytes to shared mem /tmp/vgdb-pipe-shared-mem-vgdb--by-root-on-???
在网页failure to run on armv6 following the armv6 legacy patches suggested by bug 276897找到了一个暂时的方法，就是临时禁用「vgdb」。
[::]root@freescale ~/valgrind/valgrind/bin$ ./valgrind --vgdb=no ls
[::]==== Memcheck, a memory error detector
[::]==== Copyright (C) -, and GNU GPL'd, by Julian Seward et al.
[::]==== Using Valgrind-3.11. and LibVEX; rerun with -h for copyright info
[::]==== Command: ls
[::]====
[::]ERROR: ld.so: object '/opt/valgrind/lib/valgrind/vgpreload_core-arm-linux.so' from LD_PRELOAD cannot be preloaded: ignored.
[::]ERROR: ld.so: object '/opt/valgrind/lib/valgrind/vgpreload_memcheck-arm-linux.so' from LD_PRELOAD cannot be preloaded: ignored.
[::]==== Conditional jump or move depends on uninitialised value(s)
[::]==== at 0x4909C98: index (in /lib/libc-2.11..so)
[::]====
[::]==== Conditional jump or move depends on uninitialised value(s)
[::]==== at 0x4909D90: strcmp (in /lib/libc-2.11..so)
[::]==== by 0x4910377: strcoll_l (in /lib/libc-2.11..so)
[::]====
[::]==== Conditional jump or move depends on uninitialised value(s)
[::]==== at 0x4909D98: strcmp (in /lib/libc-2.11..so)
[::]==== by 0x4910377: strcoll_l (in /lib/libc-2.11..so)
2、LD_PRELOAD错误
[::]ERROR: ld.so: object '/opt/valgrind/lib/valgrind/vgpreload_core-arm-linux.so' from LD_PRELOAD cannot be preloaded: ignored.
上述的错误，经过检查，发现：「/opt/valgrind/lib/valgrind」缺少一些「.so/共享动态库」。重新编译「Valgrind」，并且用「arm-linux-strip」将文件进行精简，顺利复制。程序也顺利运行。
四、Valgrind简介
1、Valgrind是什么？
2、Valgrind能做什么？
（1）「badapp.c」
#include <stdlib.h> void f(void)
{
int* x = malloc( * sizeof(int));
x[] = ; // problem 1: heap block overrun
} // problem 2: memory leak -- x not freed int main(void)
{
f();
return ;
}
（2）
[::]<valgrind/bin/valgrind --vgdb=no --leak-check=full ./bad1pp1
[::]==== Memcheck, a memory error detector
[::]==== Copyright (C) -, and GNU GPL'd, by Julian Seward et al.
[::]==== Using Valgrind-3.11. and LibVEX; rerun with -h for copyright info
[::]==== Command: ./bad1pp1
[::]====
[::]connect fail. ip:10.167.13.207, strlen(ip):. File:main.c, Line:
[::]Internet Fail. File: main.c, Line:
[::]==== Invalid write of size
[::]==== at 0x8414: f (badapp1.c:)
[::]==== by 0x842F: main (badapp1.c:)
[::]==== Address 0x496f050 is bytes after a block of size alloc'd
[::]==== at 0x483481C: malloc (in /opt/valgrind/lib/valgrind/vgpreload_memcheck-arm-linux.so)
[::]====
[::]====
[::]==== HEAP SUMMARY:
[::]==== in use at exit: bytes in blocks
[::]==== total heap usage: allocs, frees, bytes allocated
[::]====
[::]==== bytes in blocks are definitely lost in loss record of
[::]==== at 0x483481C: malloc (in /opt/valgrind/lib/valgrind/vgpreload_memcheck-arm-linux.so)
[::]====
[::]==== LEAK SUMMARY:
[::]==== definitely lost: bytes in blocks
[::]==== indirectly lost: bytes in blocks
[::]==== possibly lost: bytes in blocks
[::]==== still reachable: bytes in blocks
[::]==== suppressed: bytes in blocks
[::]====
[::]==== For counts of detected and suppressed errors, rerun with: -v
[::]==== ERROR SUMMARY: errors from contexts (suppressed: from )
3、Valgrind工作原理？
4、谁开发的Valgrind？
Julian Seward, from Cambridge, UK.
5、Valgrind的名称来源
From Nordic mythology. Originally (before release) the project was named Heimdall, after the watchman of the Nordic gods. He could "see a hundred miles by day or night, hear the grass growing, see the wool growing on a sheep's back" (etc). This would have been a great name, but it was already taken by a security package "Heimdal". Keeping with the Nordic theme, Valgrind was chosen. Valgrind is the name of the main entrance to Valhalla (the Hall of the Chosen Slain in Asgard). Over this entrance there resides a wolf and over it there is the head of a boar and on it perches a huge eagle, whose eyes can see to the far regions of the nine worlds. Only those judged worthy by the guardians are allowed to pass through Valgrind. All others are refused entrance. It's not short for "value grinder", although that's not a bad guess.
参考：Where does the name 'Valgrind' come from?
6、如何利用Valgrind结果？
参考：
1、应用 Valgrind 发现 Linux 程序的内存问题
2、Valgrind 基础
3、Valgrind Frequently Asked Questions
4、Valgrind官网
5、Valgrind Guide
6、Valgrind Quick Start
