How malloc_history works.. #1
Description
This may help in answering the question,
How can malloc_history command show the name of objects and call stack or more? malloc_history works well only if the target process is alive. That's the key to understand how malloc_history works, I think. Does anybody know any information about the mechanism of malloc_history?
The stack_logging_disk.c source file includes this comment:
Stack log files can be quite large and aren't useful after the process that created them no longer exists because the stack backtrace uniquing tree was only kept in the process memory, not on disk.