Valgrind 报告无效的重新分配

Question

我试图回填我对 C 内存管理的了解。我主要来自脚本编写和管理背景，我想了解有关 C 和 C++ 的更多信息。为此，我一直在阅读几本书，其中包括以下realloc用于修剪一串空格的示例：

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char* trim(char* phrase)
{
  char* old = phrase;
  char* new = phrase;

  while(*old == ' ') {
    old++;
  }

  while(*old) {
    *(new++) = *(old++);
  }

  *new = 0;

  return (char*)realloc(phrase, strlen(phrase)+1);
}

int main ()
{
  char* buffer = (char*)malloc(strlen("  cat")+1);
  strcpy(buffer, "  cat");

  printf("%s\n", trim(buffer));

  free(buffer);
  buffer=NULL;

  return 0;
}

我尽职尽责地复制了这个例子，并用c99 -Wall -Wpointer-arith -O3 -pedantic -march=native. 我没有收到任何编译错误，该应用程序运行并执行书中承诺的操作，但是当我针对 valgrind 运行它时，我收到关于 invalid 的错误realloc。

==21601== Memcheck, a memory error detector
==21601== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==21601== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==21601== Command: ./trim
==21601== 
==21601== Invalid free() / delete / delete[] / realloc()
==21601==    at 0x402B3D8: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==21601==    by 0x804844E: main (in /home/mo/programming/learning_pointers/trim)
==21601==  Address 0x4202028 is 0 bytes inside a block of size 6 free'd
==21601==    at 0x402C324: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==21601==    by 0x80485A9: trim (in /home/mo/programming/learning_pointers/trim)
==21601==    by 0x804842E: main (in /home/mo/programming/learning_pointers/trim)
==21601== 
==21601== 
==21601== HEAP SUMMARY:
==21601==     in use at exit: 4 bytes in 1 blocks
==21601==   total heap usage: 2 allocs, 2 frees, 10 bytes allocated
==21601== 
==21601== 4 bytes in 1 blocks are definitely lost in loss record 1 of 1
==21601==    at 0x402C324: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==21601==    by 0x80485A9: trim (in /home/mo/programming/learning_pointers/trim)
==21601==    by 0x804842E: main (in /home/mo/programming/learning_pointers/trim)
==21601== 
==21601== LEAK SUMMARY:
==21601==    definitely lost: 4 bytes in 1 blocks
==21601==    indirectly lost: 0 bytes in 0 blocks
==21601==      possibly lost: 0 bytes in 0 blocks
==21601==    still reachable: 0 bytes in 0 blocks
==21601==         suppressed: 0 bytes in 0 blocks
==21601== 
==21601== For counts of detected and suppressed errors, rerun with: -v
==21601== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

所以请帮助我理解为什么它被认为是无效的重新分配。例子是废话吗？有什么我想念的吗？我知道根据规范，realloc 期望指针之前已由 malloc 创建，所以是因为 realloc 在另一个函数中吗？或者 valgrind 因为它们在不同的功能中而感到困惑？我不是一个彻头彻尾的白痴（大多数时候），但现在我有点觉得自己没有看到这个问题。

提前致谢！

Answer 1

您正在尝试free使用原始指针，而不是reallocd指针。您可以通过以下方式修复它：

buffer = trim(buffer)