1

我只是使用 valgrind 的初学者。我已将 ubuntu 作为 vmWare 的一部分打开，我刚刚制作了应该显示 valgrind 错误的 ac 程序，并在 a.out 上运行了 valgrind，但我看不到这条线输出中可见的数字：使用的命令是：

valgrind --leak-check=full --track-origins=yes ./a.out

对于 C 程序如下所示：

  #include <stdlib.h>

  #define ARRAY_SIZE      (5)

  typedef char TEST_TYPE;


  void invalid_write(TEST_TYPE* array, int size)
  {
     array[size] = 5;
  }


 int main(void)
 {
    TEST_TYPE static_array[ARRAY_SIZE];
    TEST_TYPE* dynamic_array = NULL;
    TEST_TYPE* p = NULL;
    TEST_TYPE i;


    dynamic_array = (TEST_TYPE*)malloc(ARRAY_SIZE * sizeof(TEST_TYPE));
   /* ERROR 1 : Writing out of array boundaries (heap overrun) */
    invalid_write(dynamic_array, ARRAY_SIZE);
 }

输出如下所示：

==6801== Memcheck, a memory error detector
==6801== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==6801== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==6801== Command: ./a.out
==6801== 
==6801== Invalid write of size 1
==6801==    at 0x80483ED: invalid_write (in /home/jci/a.out)
==6801==    by 0x804842E: main (in /home/jci/a.out)
==6801==  Address 0x419702d is 0 bytes after a block of size 5 alloc'd
==6801==    at 0x4026444: malloc (vg_replace_malloc.c:263)
==6801==    by 0x8048416: main (in /home/jci/a.out)
==6801== 
==6801== 
==6801== HEAP SUMMARY:
==6801==     in use at exit: 5 bytes in 1 blocks
==6801==   total heap usage: 1 allocs, 0 frees, 5 bytes allocated
==6801== 
==6801== 5 bytes in 1 blocks are definitely lost in loss record 1 of 1
==6801==    at 0x4026444: malloc (vg_replace_malloc.c:263)
==6801==    by 0x8048416: main (in /home/jci/a.out)
==6801== 
==6801== LEAK SUMMARY:
==6801==    definitely lost: 5 bytes in 1 blocks
==6801==    indirectly lost: 0 bytes in 0 blocks
==6801==      possibly lost: 0 bytes in 0 blocks
==6801==    still reachable: 0 bytes in 0 blocks
==6801==         suppressed: 0 bytes in 0 blocks
==6801== 
==6801== For counts of detected and suppressed errors, rerun with: -v
==6801== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 11 from 6)

我应该如何获得这些错误的行号，以便我们可以准确地指出问题？目前使用的 valgrind 版本是 3.7.0。

4

2 回答 2

4

您需要使用调试信息构建程序，对于 gcc，您应该能够执行以下操作：

gcc -g -O0 -Wall sourcefile.c

Valgrind 然后会显示你的源代码中的行号和函数名。

于 2013-03-22T11:53:29.530 回答
0

为此，您可以使用 addr2line 工具。

addr2line --exe a.out 8048416

我假设您-g在构建对象时使用了标志：

gcc -c -g my_source1.c -o mysource1.o
gcc -c -g my_source2.c -o mysource2.o
gcc mysource1.o mysource2.o -o myapp

或者：

gcc -g my_source1.c my_source2.c -o myapp
于 2013-03-22T11:56:11.673 回答