VS.NET 2003 memory leak detection function

xiaoxiao2021-03-06  50

It didn't pay attention to this in this regard, when I was newly assigned a memory, I didn't release it, VC6 was not inspected, only through third-party tools, it is very troublesome, and also increase Test work.

For example: cdialog * p = new cdialog (), when I said such an object, I didn't release it after using it, and exited the program in the DEBUG mode of VC6. The output window will not prompt you to have memory.

And when I do the same work in VS.NET 2003, I will exit the program in Debug mode and you will prompt you to have memory leaks. .

please look below

:

! Detected memory leaks Dumping objects -> c: /test/testdlg.cpp (373): {76} client block at 0x00376938, subtype c0, 116 bytes long.a CDialog object at $ 00376938, 116 bytes longObject dump complete.

So if you want to debug your results, I suggest it to do it under VS.Net, so it is convenient, and intuitive.

转载请注明原文地址:https://www.9cbs.com/read-81668.html

New Post(0)