AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

Previous Message Next Message
Message List New Topic Print View
|
RWCox
March 17, 2021 02:57PM
The SIGABRT signal to abort the program is sent (in this case) from the memory manager. It can indicate that too much memory is being asked for by the program, or (more likely) that the program has run amok and destroyed the data structure that supports the memory manager.

This kind of error is hard to find, and impossible without being able to reproduce the problem. To go any further, we'd need a copy of all the data that you used to run 3dDeconvolve with, and the exact command line, so we can try to duplicate the problem and then figure out what the heck is happening. And then maybe fix it.
Reply Quote
RSS
Subject Author Posted

3dREMLfit from 3dDeconvolve: Fatal Signal 6 (SIGABRT) received

ruben.nechifor March 16, 2021 06:07AM

Re: 3dREMLfit from 3dDeconvolve: Fatal Signal 6 (SIGABRT) received

RWCox March 17, 2021 02:57PM

Re: 3dREMLfit from 3dDeconvolve: Fatal Signal 6 (SIGABRT) received

ruben.nechifor March 19, 2021 07:08AM