using gdb on your core file shows:#5 0x000000000046939d in abortutils::endrun (msg="") at /project/projectdirs/ccsm1/collections/cesm1_0_beta23/models/atm/cam/src/utils/abortutils.F90:36
#6 0x00000000008be2d1 in cnbalancecheckmod::cbalancecheck (lbc=-40912, ubc=-40912, num_soilc=-40912, filter_soilc=...)
at /project/projectdirs/ccsm1/collections/cesm1_0_beta23/models/lnd/clm/src/biogeochem/CNBalanceCheckMod.F90:254
#7 0x00000000009bcc10 in clm_driver::clm_drv (doalb=4294967295, nextsw_cday=1.8125, declinp1=-0.40193890144331151, declin=-0.40196795685562658, rstwr=.FALSE.,
nlend=.FALSE., rdate=
../../gdb/exec.c:614: internal-error: failed internal consistency check
A problem internal to GDB has been detected,
further debugging may prove unreliable.
I'm not sure why gdb is unhappy. However, the location of the stack traceback is consistent with the messages in the log files.The ccsm.exe executable in this directory is dated 22 August 2012. That seems like a potential problem to me. I'd recommend rebuilding the executable to be sure it's consistent with the current programming environment. At any rate the problem is not associated with the extended datasets.