我正在尝试使用 Valgrind 调试我的代码中的免费错误后的使用。
我的代码在尝试访问先前删除的对象时崩溃。在这种情况下，有没有办法使用 Valgrind 查看谁删除了对象？
我使用以下选项运行 Valgrind，但它只捕获崩溃，并显示它发生的位置。我希望获得有关对象被释放位置的详细信息:
最佳答案
这是我在这些情况下使用的:
valgrind --track-origins=yes
在释放后使用的情况下，它将向您显示释放内存/删除对象的函数的堆栈跟踪。
请阅读 Valgrind 的联机帮助页了解注意事项，特别是有关性能的注意事项。如果您的问题是并发问题，则较慢的 Valgrind 可能会更改程序的计时属性，并可能会更改(减少或增加)遇到错误的可能性。
--track-origins=<yes|no> [default: no]
Controls whether Memcheck tracks the origin of uninitialised
values. By default, it does not, which means that although it can
tell you that an uninitialised value is being used in a dangerous
way, it cannot tell you where the uninitialised value came from.
This often makes it difficult to track down the root problem.
When set to yes, Memcheck keeps track of the origins of all
uninitialised values. Then, when an uninitialised value error is
reported, Memcheck will try to show the origin of the value. An
origin can be one of the following four places: a heap block, a
stack allocation, a client request, or miscellaneous other sources
(eg, a call to brk).
For uninitialised values originating from a heap block, Memcheck
shows where the block was allocated. For uninitialised values
originating from a stack allocation, Memcheck can tell you which
function allocated the value, but no more than that -- typically it
shows you the source location of the opening brace of the function.
So you should carefully check that all of the function's local
variables are initialised properly.
Performance overhead: origin tracking is expensive. It halves
Memcheck's speed and increases memory use by a minimum of 100MB,
and possibly more. Nevertheless it can drastically reduce the
effort required to identify the root cause of uninitialised value
errors, and so is often a programmer productivity win, despite
running more slowly.
Accuracy: Memcheck tracks origins quite accurately. To avoid very
large space and time overheads, some approximations are made. It is
possible, although unlikely, that Memcheck will report an incorrect
origin, or not be able to identify any origin.
Note that the combination --track-origins=yes and
--undef-value-errors=no is nonsensical. Memcheck checks for and
rejects this combination at startup.
关于c++ - 使用Valgrind调试Free After Free，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/13665076/