[cmake-developers] [CMake 0014110]: Valgrind output should be collected via output file

Mantis Bug Tracker mantis at public.kitware.com
Wed Apr 24 07:42:30 EDT 2013


The following issue has been SUBMITTED. 
====================================================================== 
http://cmake.org/Bug/view.php?id=14110 
====================================================================== 
Reported By:                Rolf Eike Beer
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   14110
Category:                   CTest
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2013-04-24 07:42 EDT
Last Modified:              2013-04-24 07:42 EDT
====================================================================== 
Summary:                    Valgrind output should be collected via output file
Description: 
If you have tests that have a result that depends on matching their output
against a regular expressions those test will fail if valgrind reports any
errors. Valgrind offers both --log-file as well as --log-fd. As e.g. Purify is
already told to output it's finding to a file I guess it shouldn't be hard to do
the same for valgrind (Source/CTest/cmCTestMemCheckHandler.cxx).

The question is if this could have any side effect, i.e. are there any valgrind
versions that don't support that option? What happens on parallel test
execution? Or is that already disabled for memcheck runs?
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2013-04-24 07:42 Rolf Eike Beer New Issue                                    
======================================================================




More information about the cmake-developers mailing list