All geek questions in one place

Memory leak tracing using AppVerifier

I have a C ++ application that has some minimal leaks, and I would like to fix them. I use AppVerifier to dump leaked objects, and I can get the addresses and first few bytes of allocated memory.

Unfortunately, these first bytes and raw address are not enough to determine the distribution stack trace, is there a way to get a complete dump of the distribution data and find the stack that allocates memory?

I could put _ CrtSetBreakAllocthrough the leak number, but unfortunately this application is with a stream, and these numbers float up and down.

Does anyone have a suggestion that I could try?

+3
source share
2 answers

gflags (gflags + ust). , .

. , Microsoft ( C-RunTime, Gflags, UMDH, AppVerifier, LeakDiag), , . , , , ( , , , ,...).

+3

UMDH . GFlags, , . UMDH , .

, , , , . http://vld.codeplex.com

+1

Source: https://habr.com/ru/post/1793857/

More articles:


All Articles