[cmake-developers] Fwd: Bug#717144: Remove workaround-gcc296-bugs from ctest -T MemCheck

[Bill Hoffman]

FYI..


-------- Original Message --------
Subject: Bug#717144: Remove workaround-gcc296-bugs from ctest -T MemCheck
Resent-Date: Wed, 17 Jul 2013 09:45:01 +0000
Resent-From: Mathieu Malaterre <malat at debian.org>
Resent-To: debian-bugs-dist at lists.debian.org
Resent-CC: Modestas Vainius <modax at debian.org>
Date: Wed, 17 Jul 2013 11:42:12 +0200
From: Mathieu Malaterre <malat at debian.org>
Reply-To: Mathieu Malaterre <malat at debian.org>, 717144 at bugs.debian.org
To: Debian Bug Tracking System <submit at bugs.debian.org>

Package: cmake
Severity: important

By default ctest -T MemCheck runs:

35: MemCheck command: /usr/bin/valgrind "-q" "--tool=memcheck" 
"--leak-check=yes" "--show-reachable=yes" "--workaround-gcc296-bugs=yes" 
"--num-callers=50"

However as per documentation:

When enabled, assume that reads and writes some small distance below the 
stack pointer are due to bugs in GCC 2.96, and does not report them.
The "small distance" is 256 bytes by default. Note that GCC 2.96 is the 
default compiler on some ancient Linux distributions (RedHat 7.X) and
so you may need to use this option. Do not use it if you do not have to, 
as it can cause real errors to be overlooked. A better alternative is
to use a more recent GCC in which this bug is fixed.

Since GCC 2.96 never entered debian, I would really like to see this 
option removed.

Thanks

Ref:
Source/CTest/cmCTestMemCheckHandler.cxx: 
this->MemoryTesterOptions.push_back("--workaround-gcc296-bugs=yes");

.