Home/ Questions/Q 4016148
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T09:42:17+00:00

I have a C++ application that has some minimal leaks, and I would like

  • 0

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

Unfortunately, those first bytes and raw address is not enough to pinpoint the allocation stack trace, is there a method to get complete allocation data dump, and find the stack that’s allocating the memory?

I could put _CrtSetBreakAlloc via the leak number, but unfortunatelly it’s a threaded application and those numbers float up and down.

Does anyone have a suggestion what I could try?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    With the gflags utility you can enable storing call stack information (gflags +ust). However, your applications will now run slower and take more memory.

    Side-remark: To be honest, I never got all those Microsoft utilities (leak-tracing in the C-RunTime, Gflags, UMDH, AppVerifier, LeakDiag) to do exactly what I wanted. In the end, I simply wrote my own memory allocator in which I can add whatever tracing I want (call stack, red zone marking, delayed freeing, consistency checking, …).

    • 0