sfos/ledger
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Disabled a memory check when --verify is on

Browse source 
The check is not complete enough to be trustworthy.
This commit is contained in:
John Wiegley 2009-10-28 01:27:20 -04:00
parent da0f3bf14a
commit a53874d56c
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
src/utils.cc
View file

@ -190,8 +190,15 @@ static void trace_delete_func(void * ptr, const char * which)
i = freed_memory->find(ptr); i = freed_memory->find(ptr);
if (i != freed_memory->end()) if (i != freed_memory->end())
VERIFY(! "Freeing a block of memory twice"); VERIFY(! "Freeing a block of memory twice");
#if 0
// There can be memory allocated by Boost or the standard library, which
// was allocated before memory tracing got turned on, that the system
// might free for some coincidental reason. As such, we can't rely on
// this check being valid. I've seen cases where processes ran to
// completion with it on, and then others where valid processes failed.
else else
VERIFY(! "Freeing an unknown block of memory"); VERIFY(! "Freeing an unknown block of memory");
#endif
memory_tracing_active = true; memory_tracing_active = true;
return; return;
} }