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.micros
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 !!!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Ok, I can add a new header file in the solution. But then does that really need to be included in EACH cpp file I have in the Solution? It's tooo big and has many different projects inside. Some have stdafx (in that condition I'd add your new header file at the end of stdafx.h) and some don't have...
I had also tried just setting a breakpoint at the memory allocation number using this page:
http://msdn.microsoft.com/
But even that didn't do anything and when I close my application those memory allocation numbers are seen..
There are about 30 stdafx.h files in the different projects in the solution. Anyway, I'm adding that in all of them let's see.
But what about the code to be added in the cpp file? The application starts in one project and loads the dlls of all these different projects. Will it do if I only include that code in my WinMain() method in this startup project?
I am getting only 2851 errors after removing the ones the other thread you replied was getting.
(That is, commented wherever
#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif
was being used)
These errors are ranging from
>>>> The good news is that you could just add that to 'StdAfx.h', which will by included by all files anyway.
I don't think that this will work as StdAfx.h is a 'precompiled header' (PCH) which will not be really included but the 'compiled' stdafx.cpp will be used to add all the necessary code of the stdafx.h and all the symbols to any cpp which has the PCH option switched on.
Because of that the wizard puts the sequence
#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif
explicitly into each generated cpp file *below* #include stdafx.h.
Unfortunately the above macros won't work together with
#define _CRTDBG_MAP_ALLOC
#include <stdlib.h>
#include <crtdbg.h>
as there were duplicate definitions by that. Furthermore the stdlib.h and crtdbg.h already were included in stdafx.h so that they won't included again and so that the setting of the macro has no effect.
You can try to put these 3 statements as very first includes into the stdafx.h and make a rebuild. But I assume you will get a preprocessor error doing so cause the afx.h (or similar *afx.h) MUST be included first or the preprocessor breaks with error.
I would suggest you to use the
#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif
for each cpp file and put them above the first implemented function and below all includes what should work as long as you didn't include any other overload of operator 'new'.
I tried this but again .... it doesn't work and I am fed up now. The problem is there are so many projects, so many files in each project and some have overridden this new operator, and some have used the above three lines (#define _CRT and two includes one) and some this DEBUG_NEW thing. Moreover, instead of using DEBUG only after changing it through the precompiler they manually use DEBUG_NEW and I don't know why. I have given up and am trying to use this tool called DevPartner (and interestingly even that is not working after a big show off of its installation and integration with VS 2005 and internal windows etc. - but I guess re-installing that could help. Don't know anyway.)
Business Accounts
Answer for Membership
by: jkrPosted on 2009-02-09 at 09:54:42ID: 23592431
You can get the line numbr and file information from the C runtime directly, e.g.:
Add the following to a central header file:
#ifdef _DEBUG
#ifndef _DBG_NEW
#include <crtdbg.h>
inline void* __operator_new(size_t __n) {
return ::operator new(__n,_NORMAL_BLOCK,__FI
}
inline void* _cdecl operator new(size_t __n,const char* __fname,int __line) {
return ::operator new(__n,_NORMAL_BLOCK,__fn
}
inline void _cdecl operator delete(void* __p,const char*,int) {
::operator delete(__p);
}
#define _DBG_NEW new(__FILE__,__LINE__)
#define new _DBG_NEW
#endif // _DBG_NEW
#else
#define __operator_new(__n) operator new(__n)
#endif
Then, add
int tmpFlag;
// Get the current state of the flag
// and store it in a temporary variable
tmpFlag = _CrtSetDbgFlag( _CRTDBG_REPORT_FLAG );
// Turn On (OR) - Keep freed memory blocks in the
// heap’s linked list and mark them as freed
tmpFlag |= _CRTDBG_LEAK_CHECK_DF;
// Set the new state for the flag
_CrtSetDbgFlag( tmpFlag );
to your app's start code and call
_CrtDumpMemoryLeaks ();
to before the program ends and you'll get the line numbers where the allocations occured.
(Ref.: http:Q_21009673.html)