Q: Hi all, I tried out the custom kernel option (-kernel) in mincmorph. In lack of documentation I had to go through the source code to find the syntax for the input ascii kernel. In the process I stumbled upon what seems to be the use of an uninitialized variable which resulted in a segmentation fault. So my question is: Has anyone ever used the -kernel option in mincmorph successfully?

Andrew, it is line 120 in kernel_io.c that worries me (kernel is freed right before calling input_kernel). I’m using version 1.4.
http://www.bic.mni.mcgill.ca/pipermail/minc-users/2007-November/001816.html

A: > I tried out the custom kernel option (-kernel) in mincmorph. In lack of
> documentation I had to go through the source code to find the syntax for
> the input ascii kernel. In the process I stumbled upon what seems to be
> the use of an uninitialized variable which resulted in a segmentation fault.
> So my question is: Has anyone ever used the -kernel option in mincmorph> successfully?

Well it certainly works for me.. :)

Given that you seem to have the source take a look in the kernels/ directory in the mincmorph package, there are a few examples in there.

I also have a few more that I can post if others want them.

> Andrew, it is line 120 in kernel_io.c that worries me (kernel is freed
> right before calling input_kernel). I’m using version 1.4.
You lost me. Do you mean in kernel_io.c or mincmorph.c? input_kernel() is defined in kernel_io.c

In any case I am sure that there still might be a bug! It certainly has happened before this day.