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.