External Email - Use Caution
I got someone to help me, and based on what they told me the trac-all.log is where the debug information gets stored (I tried using -x +x in my bash command script and it only gave me upper level debugging information), so I have attached the trac-all.log file. I also was able to get help from someone who was able to save the core dump for when the system crashed, but it is extremely large (1.7GB). I can upload the core dump file if that would be helpful. I watched the system resources while the program ran, and I noticed that the memory usage only got up to 4% while the CPU usage was 100%, so I don't think I'm running out of memory. We looked at the core dump file, and my linux expert friend suggested that it may be a memory overflow error because it references memory at 0x0000000etc.
[image: image.png] unfortunately, without the source code to help us interpret the core dump, I don't think I can provide much more in the way of specific information. Please let me know if there's somewhere I can upload the core dump if you want to look at it.
Thanks!
On Mon, Oct 29, 2018 at 1:32 AM fsbuild fsbuild@contbay.com wrote:
External Email - Use CautionHello Jon,
Can you get any stack or backtrace information after the segfault occurs ?, e.g., Mac OS has the option to display the crash report with a trace. On Linux you could run thru gdb and get a back trace. This would help us to see where the code is exiting.
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
