Ziad,

I can confirm that that is the very last thing that is output by the trace. The very next item is 'Segmentation Fault' printed to stderr. So if I allow the trace to print to the screen the end of it is....



+++++SUMA_RegisterEngineListCommand [5]: ENTRY (file=SUMA_ParseCommands.c line=882)
** Memory usage: chunks=378 bytes=65318602
-----SUMA_RegisterEngineListCommand [5]: EXIT (file=SUMA_ParseCommands.c line=1343)
** Memory usage: chunks=378 bytes=65318602


I am a little unsure what you mean when you ask it it occurs 'each' time there is a node that is not part of any triangles. Every time there is a surface that contains one of these nodes suma seg faults, yes. However, even though there may be two surfaces in a given spec file that have the error, obviously only the first one will seg fault since that stops suma from getting to the next surface read.

Just in case it might be helpful, I ran the exact same dataset and command on the working RedHat system to see what should come after (or at) the Seg Fault. I have uploaded that normal execution to iggy_working_trace.tgz. I noted that all the entry and exit bytes are different, but I'm not sure what that means, if anything.

Thanks so much for the effort that you're putting into this. I greatly appreciate it.

Iggy