[Insight-users] CableSwig using all memory

[Curzio Basso]

Hi,

I got a strange (for me) problem trying to compile WrapITK (on
ITK-3.6.0), more specifically
the IntensityFilters part. The problem however might apply also to other
wrapper modules. Essentially, what happens is that cswig slowly eats
up all memory of my machine (2GB!), until it is killed by the OS. As an example,
this is the output I got last time I tried:

[ 84%] Generating wrap_itkMaskNegatedImageFilterPython.cxx
/bin/sh: line 1:  3455 Killed
../../../../Utilities/CableSwig-ITK-3.6.0/bin/cswig
-l/home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/SWIG/IntensityFilters.swg
-l/home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/SWIG/itk.swg
-l/home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/SWIG/BaseNumerics.swg
-l/home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/SWIG/Base.swg
-I/home/basso/work/InsightToolkit-3.6.0/Utilities/CableSwig-ITK-3.6.0/SWIG/Lib
-w362 -w389 -w467 -w503 -w508 -w509 -w516 -noruntime -fcompact -Cindex
/home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/ClassIndex/Base.mdx
-Cindex /home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/ClassIndex/BaseNumerics.mdx
-Cindex /home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/ClassIndex/IntensityFilters.mdx
-depend /home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/Modules/IntensityFilters/wrap_itkMaskNegatedImageFilter.xml.depend
-outdir /home/basso/work/InsightToolkit-3.6.0/bin -o
/home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/Modules/IntensityFilters/wrap_itkMaskNegatedImageFilterPython.cxx
-c++ -I/home/basso/work/InsightToolkit-3.6.0/Utilities/CableSwig-ITK-3.6.0/SWIG/Lib/python
-python /home/basso/work/InsightToolkit-3.6.0/Wrapping/WrapITK/Modules/IntensityFilters/wrap_itkMaskNegatedImageFilter.xml
make[2]: *** [Wrapping/WrapITK/Modules/IntensityFilters/wrap_itkMaskNegatedImageFilterPython.cxx]
Error 137
make[1]: *** [Wrapping/WrapITK/Modules/IntensityFilters/CMakeFiles/_IntensityFiltersPython.dir/all]
Error 2
make: *** [all] Error 2

Someone has an idea of how to circumvent the problem short of manually
"blacklist" the
problematic files?

thanks
q.

-- 
http://www.disi.unige.it/person/BassoC/