	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

5.4

VC++ Memory Leak Detection not working

Asked by piyush_soni in Debugging Software for Development, Editors IDEs, C++ Programming Language

Tags: Memory Leak detection, breakpoint at memory allocation number

Hi,
My big win32 VC++ solution has many memory leaks :). But by default, Visual Studio 2005 shows only the memory allocation numbers and blocks. No filename and line number.

I gone through all the memory detection pages of Microsoft and tried what's written there. Though it worked in a small sample win32 applicatiion I tried, but not in my big solution. I have included the lines

#define _CRTDBG_MAP_ALLOC
#include <stdlib.h>
#include <crtdbg.h>

at the end of the stdafx.h file in each project. (a few projects my solution uses are plain win32 projects that don't have stdafx.h and cpp. I included the above lines in a header file which every source file uses in those projects). But still when I close my application, the debugger shows only the same info, nothing more: no filename, line number etc.

Then I thought of setting a "breakpoint at memory allocation number"(http://msdn.microsoft.com/en-us/library/w2fhc9a3(VS.80).aspx) so that I will anyway know where the leak is occurring. But even that is not making the debugger break at those locations. Why would it happen?

Any simpler way of doing these things? Any way that I don't have to include these things in every file but just one?

Thanks a lot for your help !!!

View the Solution FREE for 30 Days

20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. jcgriff29,800
2. chris_bot...6,000
3. roman24,600
4. abel4,500
5. duncan_roe4,000
5. madprogr...4,000
7. epasquier3,000
8. emoreau2,500
8. meverest2,500
8. jkr2,500
8. ragi00172,500
8. TechSoEasy2,500
8. apresto2,500
8. doades2,500
15. nobus2,400
16. MrClyfar2,000
16. Jbamaral2,000
16. locke_a2,000
16. t0t02,000
16. Sethi2,000
16. rg202,000
16. joinaunion2,000
16. oBdA2,000
16. gtokas2,000
16. McKnife2,000
16. nsr812,000
16. Snarf00012,000
16. mwvisa12,000
16. dericstone2,000
16. TeraByte...2,000
16. p_davis2,000
16. David-Ho...2,000
16. Ray_Pas...2,000
16. EMB012,000
16. Gary_Th...2,000
16. Jones9112,000
16. oklit2,000
16. treeandrew2,000
16. hathehariken2,000
16. pcelba2,000
16. Aleksei_...2,000
16. leakim9712,000

1. jcgriff29,800
2. jkr8,500
3. chris_bot...6,000
4. roman24,600
5. abel4,500
6. Dhaest4,000
6. sunnycoder4,000
6. duncan_roe4,000
6. madprogr...4,000
10. meverest3,500
11. MrClyfar3,000
11. epasquier3,000
13. emoreau2,800
14. ragi00172,500
14. TechSoEasy2,500
14. apresto2,500
14. jgordos2,500
14. doades2,500
19. nobus2,400
20. Qlemo2,150
21. Jbamaral2,000
21. dbrunton2,000
21. locke_a2,000
21. ericpete2,000
21. t0t02,000
21. Sethi2,000
21. rg202,000
21. logudotcom2,000
21. joinaunion2,000
21. oBdA2,000
21. mrGreen2,000
21. twoboats2,000
21. basicinsti...2,000
21. johnb67672,000
21. scrathcyboy2,000
21. gtokas2,000
21. pmascari2,000
21. dampsey2,000
21. McKnife2,000
21. nsr812,000
21. mtz1of42,000
21. vadimrapp12,000
21. Snarf00012,000
21. mwvisa12,000
21. evilrix2,000
21. ororiole2,000
21. dericstone2,000
21. TeraByte...2,000
21. p_davis2,000
21. David-Ho...2,000
21. Ray_Pas...2,000
21. MrHusy2,000
21. pcsmitpra2,000
21. slam692,000
21. EMB012,000
21. Gary_Th...2,000
21. paulsolov2,000
21. Jones9112,000
21. oklit2,000
21. treeandrew2,000
21. hathehariken2,000
21. pcelba2,000
21. Aleksei_...2,000
21. leakim9712,000

VC++ Memory Leak Detection not working

Asked by piyush_soni in Debugging Software for Development, Editors IDEs, C++ Programming Language

Tags: Memory Leak detection, breakpoint at memory allocation number

About this solution