Featured post
visual studio 2008 - _CrtDumpMemoryLeaks truncated output? -
i trying use visual studio's capability detect memory leaks, keep getting truncated output, like:
dumping objects -> {174} normal block @ 0x0099adb8, 48 bytes long. data: <h:\najnovije\tru> 68 3a 5c 6e 61 6a 6e 6f 76 69 6a 65 5c 74 72 75 {170} normal block @ 0x0099ad58, 32 bytes long. data: <h:\najnovije\tru> 68 3a 5c 6e 61 6a 6e 6f 76 69 6a 65 5c 74 72 75 object dump complete.
what doing wrong? added
#define _crtdbg_map_alloc #include <stdlib.h> #include <crtdbg.h>
to beginning of code.
thank you.
this output not truncated. it's meant used in way.
try give deeper observation program. can find visual studio (more precisely, ~99% of time) gives same leaking address 0x0099adb8 , 0x0099ad58, if use same test steps.
now, need setup data breakpoints break on changes of these 2 addresses. break @ beginning of program, select debug->new breakpoint->new data breakpoint, type in address. in case, need create 2 of them: 1 0x0099adb8 , other 0x0099ad58. stopped @ code instantiate block of memory, gives point leak from.
there can cases got different leaking address every time. in case, you'd better use gflags , windbg instead have chance diff memory contents , start there.
- Get link
- X
- Other Apps
Comments
Post a Comment