Control: severity -1 important On Wed, Jul 17, 2013 at 11:58 AM, Modestas Vainius <mo...@debian.org> wrote: > On Wednesday 17 of July 2013 11:42:12 Mathieu Malaterre wrote: >> 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. > > I'm against changing Debian cmake behaviour (in comparison to vanilla one) > unless it is absolutely necessary.
Define "absolutely necessary" ? As DD, you do do know about DFSG #4, right ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
