我在调试valgrind错误时相对较新，这让我很难受。
==1920== Invalid write of size 1
==1920== at 0x4C2ECC7: strcpy (/builddir/build/BUILD/valgrind-3.11.0/memcheck/../shared/vg_replace_strmem.c:506)
==1920== by 0x1D533B57: CSR_bullet (packages/tests-vg/vetr/src/cstringr.c:448)
... redacted (see end for full error)
==1920== Address 0x1bd1be1f is 5,599 bytes inside a block of size 7,960 alloc'd
==1920== at 0x4C2BBAD: malloc (/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc/vg_replace_malloc.c:299)
==1920== by 0x4F3D3E: GetNewPage (svn/R-devel/src/main/memory.c:879)
... redacted (see end for full error)
请注意，这是 1 字节 and Alloc'd block内部。我看到了类似的错误，这些错误涉及在以后或之前或自由块写作，甚至写入写作大小大于块的末端 - 地址（因此溢出），但我找不到像这个。
这是在此代码的R Cran Check Farm上发生的。
我无法在OSX上或Linux VM上使用Valgrind在本地重现该错误。
除此之外，错误对我没有意义。为什么我不能在分配的块的中间写1个字节？这一切都在R内部运行，因此我猜可能的分配是由程序的另一部分进行的，并且是某种程度上保留的（一个可能发生的暗示是，我从R要求的分配均小于60当错误显示时字节），但是我不知道这是否是Valgrind可以检测到的。
完整错误：
==1920== Invalid write of size 1
==1920== at 0x4C2ECC7: strcpy (/builddir/build/BUILD/valgrind-3.11.0/memcheck/../shared/vg_replace_strmem.c:506)
==1920== by 0x1D533B57: CSR_bullet (packages/tests-vg/vetr/src/cstringr.c:448)
==1920== by 0x1D53317D: CSR_bullet_ext (packages/tests-vg/vetr/src/cstringr-ext.c:107)
==1920== by 0x4852BD: do_dotcall (svn/R-devel/src/main/dotcode.c:1252)
==1920== by 0x4C274D: Rf_eval (svn/R-devel/src/main/eval.c:728)
==1920== by 0x4C3AB5: R_execClosure (svn/R-devel/src/main/eval.c:1617)
==1920== by 0x4C2391: Rf_eval (svn/R-devel/src/main/eval.c:747)
==1920== by 0x4C29E0: forcePromise (svn/R-devel/src/main/eval.c:520)
==1920== by 0x4C27A1: Rf_eval (svn/R-devel/src/main/eval.c:647)
==1920== by 0x4C7746: do_withVisible (svn/R-devel/src/main/eval.c:2998)
==1920== by 0x4F7104: do_internal (svn/R-devel/src/main/names.c:1363)
==1920== by 0x4B553B: bcEval (svn/R-devel/src/main/eval.c:6503)
==1920== Address 0x1bd1be1f is 5,599 bytes inside a block of size 7,960 alloc'd
==1920== at 0x4C2BBAD: malloc (/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc/vg_replace_malloc.c:299)
==1920== by 0x4F3D3E: GetNewPage (svn/R-devel/src/main/memory.c:879)
==1920== by 0x4F5814: Rf_allocVector3 (svn/R-devel/src/main/memory.c:2659)
==1920== by 0x4CAEAF: Rf_allocVector (svn/R-devel/src/include/Rinlinedfuns.h:247)
==1920== by 0x4CAEAF: do_growconst (svn/R-devel/src/main/eval.c:7490)
==1920== by 0x4B64BD: bcEval (svn/R-devel/src/main/eval.c:6483)
==1920== by 0x4C2207: Rf_eval (svn/R-devel/src/main/eval.c:624)
==1920== by 0x4C3AB5: R_execClosure (svn/R-devel/src/main/eval.c:1617)
==1920== by 0x4BAE13: bcEval (svn/R-devel/src/main/eval.c:6454)
==1920== by 0x4C2207: Rf_eval (svn/R-devel/src/main/eval.c:624)
==1920== by 0x4C3AB5: R_execClosure (svn/R-devel/src/main/eval.c:1617)
==1920== by 0x4BAE13: bcEval (svn/R-devel/src/main/eval.c:6454)
==1920== by 0x4C2207: Rf_eval (svn/R-devel/src/main/eval.c:624)
使用内存池时可能会发生这种错误。
通常，LIB或应用程序（例如R）可以构建自己的分配器通过获得大块，例如从malloc，然后分配小块从这些大块中。Valgrind有一些客户请求允许描述这些块（大或内部较小的块）及其分配。
使用此类客户端请求，您可能有一部分分配的块实际上，这被标记为无法寻址。
查看堆栈跟踪条目：
== 1920 ==== by 0x4f3d3e：getNewPage（svn/r-devel/src/main/mement.c：879）
上面的解释看起来很合理。
这可能表明r中的某个地方有一个真正的错误和/或R分配器描述其内存池到Valgrind