Run the test suite under Valgrind
Summary
It's pretty hard to debug full applications with valgrind because it's pretty slow, but running the unit tests is feasible and should already uncover some issues. Here is the current status of every test under valgrind:
Memcheck clean tests (fixed on at least a branch, not necessarily merged yet)
-
filterVRRenderTest -
fwActivitiesTest -
fwAtomConversionTest -
fwAtomsBoostIOTest -
fwAtomsTest -
fwCommandTest -
fwComTest -
fwCoreTest -
fwDataCampTest -
fwDataIOTest -
fwDataTest -
fwDataToolsTest -
fwDcmtkIOTest -
fwDicomIOFilterTest -
fwGdcmIOTest -
fwItkIOTest -
fwJobsTest -
fwLogTest -
fwMathTest -
fwMDSemanticPatchTest -
fwMedDataToolsTest -
fwMemoryTest -
fwPacsIOTest -
fwPreferencesTest -
fwRuntimeTest -
fwServicesTest -
fwStructuralPatchTest -
fwTestTest -
fwThreadTest -
fwToolsTest -
fwVtkIOTest -
fwZipTest -
ioITKTest -
ioPacsTest -
ioVtkGdcmTest -
ioVTKTest -
patchMedicalDataTest -
scene2DTest -
vtkGdcmIOTest
Memcheck errors/memory leaks
- fwGuiQtTest
- Issues look harmless, suppressed
- fwNetworkIOTest
- Issues look harmless, suppressed
- fwMedDataTest
-
Memory leaks in AttachmentSeriesTest
(fixed by deprecatingAttachmentSeries
)
-
- fwMedDataCampTest
-
Memory leaks, probably same problem as fwMedDataCampTest
(fixed by deprecatingAttachmentSeries
)
-
- guiQtTest
- Issues look harmless, suppressed
- ioAtomsTest
-
Some memory leaks (hard to fix, design problem regarding memory ownership between atoms and data)
-