I finally got around to running the code with cosmomc_debug and this is what it returned:
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
cosmomc_debug 0000000000DCBFF3 Unknown Unknown Unknown
libpthread-2.28.s 0000152C9ED52B20 Unknown Unknown Unknown
cosmomc_debug 00000000009B3E53 gaugeinterface_mp 242 equations.f90
cosmomc_debug 00000000009BA2AE gaugeinterface_mp 424 equations.f90
the last line was then repeated several times and then it lists
cosmomc_debug 0000000000AC1E8A cambmain_mp_gettr 1144 cmbmain.f90
cosmomc_debug 0000000000AC14EC cambmain_mp_trans 1123 cmbmain.f90
libiomp5.so 0000152C9FDCFD43 __kmp_invoke_micr Unknown Unknown
libiomp5.so 0000152C9FD5F63F Unknown Unknown Unknown
libiomp5.so 0000152C9FD5E65C Unknown Unknown Unknown
libiomp5.so 0000152C9FDD02FB Unknown Unknown Unknown
libpthread-2.28.s 0000152C9ED4814A Unknown Unknown Unknown
libc-2.28.so 0000152C9E875F23 clone Unknown Unknown
--------------------------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
forrtl: error (78): process killed (SIGTERM)
I think the rest of the .err output is just related to the rest of the processes being canceled prematurely.
If you have any thoughts on what information this might contain, that would be extremely helpful.
If it is useful, I have set stop_on_error = F.
It is running again so that I can see if these same tracebacks appear when it crashes next time...
In the meantime, is there a way to get output that shows the cosmological parameters at each point of each chain and whether or not the Cls were successfully computed? If I could determine if there is some combination of parameters for which CAMB is failing that would be very helpful.