Add Runtime Options for logMsgAbort and abort

[danrosen25]

• use ESMF_RUNTIME_LOGMSGABORT to set logMsgAbort for ESMF logs
• use ESMF_RUNTIME_ABORT to call sigquit for ESMF_Abort

Closes #296

Testing Option 1 (uses an ESMF_Initialize configuration file)

Initialize ESMF

call ESMF_Initialize(configFilenameFromArgNum=1, configFileName="esmf.cfg", &
  defaultDefaultCalKind=ESMF_CALKIND_GREGORIAN, rc=rc)

esmf.cfg

ESMF_RUNTIME_LOGMSGABORT: "ESMF_LOGMSG_ERROR" # calls ESMF_Abort if ERROR is reported to ESMF logs
ESMF_RUNTIME_ABORT: "SIGABRT" # signals abort if ESMF_Abort is called

Testing Option 2 (uses environment variables)

set environment variables

export ESMF_RUNTIME_LOGMSGABORT="ESMF_LOGMSG_ERROR"
export ESMF_RUNTIME_ABORT="SIGABRT" # or "SIGQUIT"

Test Application

esmf_abort.tar.gz

[danrosen25]

I spoke with the team and they like this feature as an alternative method for debugging. It extends the capability of setting logMsgAbort for ESMF logs to a runtime configurable option. It also extents the capability of ESMF_Abort to call SIGQUIT (backtrace and coredump) instead of MPI_Abort, also a runtime configurable option.

The note they gave me today is that users would probably want to set this in code. This is something we can discuss as it probably would exist as a flag for the VM.