heu*_*cus 4 c automake valgrind autotools libtool
我正在使用automake编译一个项目,但是当尝试在生成的可执行文件上运行valgrind时,它没有按预期运行,在实际执行我要检查的代码之前似乎运行了8次,并且该部分的堆摘要代码根本不显示:
==4601== Memcheck, a memory error detector
==4601== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==4601== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==4601== Command: ./launcher -g ../data/params.txt
==4601==
==4605==
==4605== HEAP SUMMARY:
==4605== in use at exit: 0 bytes in 0 blocks
==4605== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4605==
==4605== All heap blocks were freed -- no leaks are possible
==4605==
==4605== For counts of detected and suppressed errors, rerun with: -v
==4605== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4604==
==4604== HEAP SUMMARY:
==4604== in use at exit: 0 bytes in 0 blocks
==4604== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4604==
==4604== All heap blocks were freed -- no leaks are possible
==4604==
==4604== For counts of detected and suppressed errors, rerun with: -v
==4604== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4606==
==4606== HEAP SUMMARY:
==4606== in use at exit: 0 bytes in 0 blocks
==4606== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4606==
==4606== All heap blocks were freed -- no leaks are possible
==4606==
==4606== For counts of detected and suppressed errors, rerun with: -v
==4606== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4608==
==4608== HEAP SUMMARY:
==4608== in use at exit: 0 bytes in 0 blocks
==4608== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4608==
==4608== All heap blocks were freed -- no leaks are possible
==4608==
==4608== For counts of detected and suppressed errors, rerun with: -v
==4608== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4607==
==4607== HEAP SUMMARY:
==4607== in use at exit: 0 bytes in 0 blocks
==4607== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4607==
==4607== All heap blocks were freed -- no leaks are possible
==4607==
==4607== For counts of detected and suppressed errors, rerun with: -v
==4607== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4610==
==4610== HEAP SUMMARY:
==4610== in use at exit: 0 bytes in 0 blocks
==4610== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4610==
==4610== All heap blocks were freed -- no leaks are possible
==4610==
==4610== For counts of detected and suppressed errors, rerun with: -v
==4610== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4613==
==4613== HEAP SUMMARY:
==4613== in use at exit: 0 bytes in 0 blocks
==4613== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4613==
==4613== All heap blocks were freed -- no leaks are possible
==4613==
==4613== For counts of detected and suppressed errors, rerun with: -v
==4613== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4614==
==4614== HEAP SUMMARY:
==4614== in use at exit: 0 bytes in 0 blocks
==4614== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4614==
==4614== All heap blocks were freed -- no leaks are possible
==4614==
==4614== For counts of detected and suppressed errors, rerun with: -v
==4614== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
[Program output appears here, nothing appears afterwards]
以前,在使用标准makefile进行编译时,没有这样的问题,valgrind会显示出我预期的结果.在makefile.am我使用的编译目录如下:
lib_LTLIBRARIES = libfile_util.la libmath_util.la libgeneral_util.la libparamlist.la
libfile_util_la_SOURCES = file_util.c file_util.h
libmath_util_la_SOURCES = math_util.c math_util.h
libgeneral_util_la_SOURCES = general_util.c general_util.h
libparamlist_la_SOURCES = paramlist.c paramlist.h
bin_PROGRAMS = launcher
generator_CFLAGS = -I/usr/include/muParser
generator_SOURCES = generator.c generator.h
estimator_SOURCES = estimator.c estimator.h
estimator_iwls_SOURCES = estimator_IWLS.c estimator.h
estimator_piecewise_SOURCES = estimator_IWLS.c estimator_piecewise.c estimator.h
estimator_baseline_SOURCES = estimator_IWLS.c estimator_piecewise.c estimator_baseline.c estimator.h
launcher_CFLAGS = -I/usr/include/muParser
launcher_SOURCES = launcher.c generator.c estimator.c estimator.h generator.h
generator_LDADD = libfile_util.la libmath_util.la libgeneral_util.la libparamlist.la
launcher_LDADD = libfile_util.la libmath_util.la libgeneral_util.la libparamlist.la
estimator_iwls_LDADD = libfile_util.la libmath_util.la libgeneral_util.la libparamlist.la
estimator_piecewise_LDADD = libfile_util.la libmath_util.la libgeneral_util.la libparamlist.la
estimator_baseline_LDADD = libfile_util.la libmath_util.la libgeneral_util.la libparamlist.la
这个问题与automake编译文件的方式有关吗？如果是这样,我在makefile中做错了什么？
因为launcher正在使用libtool库,所以构建目录中的文件只是一个shell脚本,它设置必要的环境变量来运行真正的二进制文件(通常隐藏在其中.libs/).在该脚本上运行valgrind将调试执行脚本的shell,而不是真正的二进制文件.
等执行任何命令的合适方式valgrind或gdb上一个二进制的libtool是经由libtool命令:
libtool --mode=execute valgrind ./launcher -g ../data/params.txt
您甚至可以将其缩写为:
libtool e valgrind ./launcher -g ../data/params.txt
无论launcher编译方式如何,这都有效.
相关的libtool文档在这里.