walkero
/
cppcheck
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Memory leak : a little different handling when the callstack gets too big

This commit is contained in:
Daniel Marjamäki 2009-01-01 16:10:10 +00:00
parent b7b737c8f2
commit 35cdb6b0ba
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
checkmemoryleak.cpp
View File

@ -213,7 +213,7 @@ const char * CheckMemoryLeakClass::call_func( const TOKEN *tok, std::list<const
return 0; return 0;
if ( callstack.size() > 2 ) if ( callstack.size() > 2 )
return "dealloc"; return "dealloc_";
const char *funcname = tok->aaaa(); const char *funcname = tok->aaaa();
for ( std::list<const TOKEN *>::const_iterator it = callstack.begin(); it != callstack.end(); ++it ) for ( std::list<const TOKEN *>::const_iterator it = callstack.begin(); it != callstack.end(); ++it )
@ -1102,7 +1102,7 @@ void CheckMemoryLeakClass::CheckMemoryLeak_CheckScope( const TOKEN *Tok1, const
tok2->str("use"); tok2->str("use");
else if (tok2->str() == "&use2") else if (tok2->str() == "&use2")
tok2->str(";"); tok2->str(";");
else if (tok2->str() == "recursive") else if (tok2->str() == "recursive" || tok2->str() == "dealloc_")
tok2->str("dealloc"); tok2->str("dealloc");
} }