[MINC-development] minctracc and large(ish) input files

[Claude LEPAGE]

Hi Andrew,

In such cases, valgrind is my friend. You can also run
through gdb. 

There are lots of instances in our tools that don't verify
for properly allocated memory.

Claude

> Has anyone else had minctracc fail (segfault) on sizeable but not
> massive input files?
> 
> In my case the input file is big but not ginormous:
> 
> file: b.mnc
> image: unsigned byte 0 to 255
> image dimensions: zspace yspace xspace
>     dimension name         length         step        start     dircos
>     --------------         ------         ----        -----     ------
>     zspace                    150          0.5       -124.2     0 0 1
>     yspace                   1311          0.5      -327.15     0 1 0
>     xspace                    679          0.5       -169.2     1 0 0
> 
> And this will segfault it:
> 
>    ~/cvs/registration/mni_autoreg/minctracc/Main/minctracc -no_super
> -transformation ident.xfm -clobber -nonlinear -iterations 1 -step 32
> 32 32 -debug b.mnc b.mnc /tmp/out.xfm
> 
> It seems to die while doing the amoeba setup step but this is likely
> just memory being overstepped from somewhere else.
> 
> Anyone (Claude and his big brain!) have any insights as to which
> particular rabbit hole I should go looking down first?
> 
> 
> ta