1

我从 gdb 收到以下错误：

*** glibc detected *** /.root0/autohome/u132/hsreekum/ipopt/ipopt/debug/Ipopt/examples/ex3/ex3: free(): invalid next size (fast): 0x0000000120052b60 ***

这是回溯：

#0  0x000000555626b264 in raise () from /lib/libc.so.6
#1  0x000000555626cc6c in abort () from /lib/libc.so.6
#2  0x00000055562a7b9c in __libc_message () from /lib/libc.so.6
#3  0x00000055562aeabc in malloc_printerr () from /lib/libc.so.6
#4  0x00000055562b036c in free () from /lib/libc.so.6
#5  0x000000555561ddd0 in Ipopt::TNLPAdapter::~TNLPAdapter ()
   from /home/ba01/u132/hsreekum/ipopt/ipopt/build/lib/libipopt.so.1
#6  0x00000055556a9910 in Ipopt::GradientScaling::~GradientScaling ()
   from /home/ba01/u132/hsreekum/ipopt/ipopt/build/lib/libipopt.so.1
#7  0x00000055557241b8 in Ipopt::OrigIpoptNLP::~OrigIpoptNLP ()
   from /home/ba01/u132/hsreekum/ipopt/ipopt/build/lib/libipopt.so.1
#8  0x00000055556ae7f0 in Ipopt::IpoptAlgorithm::~IpoptAlgorithm ()
   from /home/ba01/u132/hsreekum/ipopt/ipopt/build/lib/libipopt.so.1
#9  0x0000005555602278 in Ipopt::IpoptApplication::~IpoptApplication ()
   from /home/ba01/u132/hsreekum/ipopt/ipopt/build/lib/libipopt.so.1
#10 0x0000005555614428 in FreeIpoptProblem ()
   from /home/ba01/u132/hsreekum/ipopt/ipopt/build/lib/libipopt.so.1
#11 0x0000000120001610 in main () at ex3.c:169`

这是代码Ipopt::TNLPAdapter::~TNLPAdapter ()

  TNLPAdapter::~TNLPAdapter()
  {
    delete [] full_x_;
    delete [] full_lambda_;
    delete [] full_g_;
    delete [] jac_g_;
    delete [] c_rhs_;
    delete [] jac_idx_map_;
    delete [] h_idx_map_;
    delete [] x_fixed_map_;
    delete [] findiff_jac_ia_;
    delete [] findiff_jac_ja_;
    delete [] findiff_jac_postriplet_;
    delete [] findiff_x_l_;
    delete [] findiff_x_u_;
  }

我的问题是：为什么使用free()时会抛出错误？另外，我想单步执行，以便查看导致错误的解除分配。我相信错误发生在外部库（IPOPT）中，但我已使用调试标志编译它；这足够了吗？~TNLPAdapter()delete[]~TNLPAdapter()

4

1 回答 1

5

new[]/ 后面的原始内存分配/释放机制通常与/delete[]使用的相同。原始内存分配/释放函数的标准库实现/实际上可以直接调用和. 因此，即使您使用.mallocfreeoperator new[]operator delete[]mallocfreefreedelete []

您收到的错误表明堆的完整性被违反。堆已损坏。问题的根源可能在这个函数中（双重释放？）或在一些完全不同的地方（双重释放或内存溢出？）。无法从您发布的代码中说出发生了什么。

找出delete []报告问题的特定调用，并查看是否有其他代码覆盖了该内存块。或者只是使用一些外部工具，如 valgrind 来抓捕罪犯。

于 2012-08-29T21:30:25.470 回答