diff options
| author | Rolf Eike Beer <eike@sf-mail.de> | 2013-05-06 20:04:30 (GMT) |
|---|---|---|
| committer | Rolf Eike Beer <eike@sf-mail.de> | 2013-05-09 17:24:53 (GMT) |
| commit | 3b5b758915125f19cb57994601cc0cd68293fe2b (patch) | |
| tree | 1e34444215b625b919bb806feb32da51eefe06b5 | |
| parent | 775225319295c08d2d6d7bb84010e4494d1bc5d0 (diff) | |
| download | CMake-3b5b758915125f19cb57994601cc0cd68293fe2b.zip CMake-3b5b758915125f19cb57994601cc0cd68293fe2b.tar.gz CMake-3b5b758915125f19cb57994601cc0cd68293fe2b.tar.bz2 | |
CTest: drop suppression for gcc 2.9.6 errors from default Valgrind flags
The --workaround-gcc296-bugs has been part of the default Valgrind flags since
Valgrind support was added in commit 5b232ded151fc22144978b74cdaf7031d466e527
(ENH: Add initial memory check support which works for Valgrind, 2003-12-15).
The Valgrind manpage says that this option should be avoided if not really
needed as it may cause real errors to get ignored. If someone uses a compiler
that really needs the flag this flag should be set by the user explicitely.
Most users will never set any flags and probably never notice that they use a
flag they shouldn't.
| -rw-r--r-- | Source/CTest/cmCTestMemCheckHandler.cxx | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/Source/CTest/cmCTestMemCheckHandler.cxx b/Source/CTest/cmCTestMemCheckHandler.cxx index 280faa0..19c156e 100644 --- a/Source/CTest/cmCTestMemCheckHandler.cxx +++ b/Source/CTest/cmCTestMemCheckHandler.cxx @@ -491,7 +491,6 @@ bool cmCTestMemCheckHandler::InitializeMemoryChecking() this->MemoryTesterOptions.push_back("--tool=memcheck"); this->MemoryTesterOptions.push_back("--leak-check=yes"); this->MemoryTesterOptions.push_back("--show-reachable=yes"); - this->MemoryTesterOptions.push_back("--workaround-gcc296-bugs=yes"); this->MemoryTesterOptions.push_back("--num-callers=50"); } if ( this->CTest->GetCTestConfiguration( |