[MINC-users] strange mnc2nii behaviour

[Soren Christensen]

Hi,
 Thanks for the help with mnc2nii earlier in the week. Used
correct_header and still use MINC 1.5 for now so apologies if this is
not a bug in MINC 2.0:
I Had mnc2nii crash on a long filename - here's and example (with a
filename to illustrate the point):
mnc2nii -signed -float t.mnc 0123456789012345678901234567890123456789.nii
... The usual header output
MINC type 5 signed 1
Segmentation fault


When making the filename shorter or longer:
mnc2nii -signed -float t.mnc 01234567890123456789012345678901234567890.nii
... The usual header output
MINC type 5 signed 1
0: 256 0 1
1: 124 1 1
2: 256 2 1
bytes per voxel 4
# of voxels 8126464
0 0 0 => -105.570312 -105.400002 -90.670311
10 0 0 => -96.976562 -105.400002 -90.670311
0 10 0 => -105.570312 -90.400002 -90.670311
0 0 10 => -105.570312 -105.400002 -82.076561
10 10 10 => -96.976562 -90.400002 -82.076561

= no errors


Is there something going on with a string pointer somewhere in nii2mnc?

Cheers
Soren