windbg

I used the !address -RegionusageIsVAD and found an entry that is very huge in size. How can i view who wrote this data and what data is in that specitic address? Exmaple output: 099230000 : 099230000 - 01000000 Type 00020000 MEM_PRIVATE Protect 00000004 PAGE_READWRITE State 00001000 MEM_COMMIT Usage RegionUsageIsVAD So i want to see what data is in this address and who allocated it. High RegionUsageIsVAD typically comes from 2 reasons : this is a .NET application. In this case, the CLR allocates a block of memory and performs its own allocations inside it. You can troubleshoot this kind of

Hello I have a leak in my WPF application and I'm trying to use the memory dump file to track down where the problem is. Using WinDbg and SOS I couldn't find anything suspicious. Then I tried DebugDiag and I got that Microsoft VC Runtime Heap (private) has 1,42 GBytes of commited memory. Do you know why does this happen? Heap 1 - 0x003b0000 Heap Name Microsoft VC Runtime Heap (private) Heap Description This is a private CRT heap used by mscoreei Reserved memory 1,43 GBytes Committed memory 1,42 GBytes(99,21% of reserved) Uncommitted memory 11,48 MBytes(0,79% of reserved) Number of heap

Is there a set of CDB commands for setting a breakpoint based on a line number? It seems that there is no "direct" one. Actually it seems that CDB knowledge is falling into a black hole and it's getting harder and harder to find resources on the Internet. My CDB setup cdb -c "l+*;.lines" and later I add the source lsf mySource.d Currently I put hard-coded breakpoints with a mixin enum brk = "debug{asm{int 3;}}"; // code mixin(brk); But it's not a viable solution. The syntax to break in source line mode, is well explained here or here , e.g: bp `mod!source.c:12`; And to stop on a particular