Adding debugging info#
If you cannot find the reason of the crash in the log files, there are two ways to add more debugging information.
Increase the value of the run-time xml variable
INFO_DBUG
(This does NOT require rebuilding):
./xmlchange INFO_DBUG=2.
This adds more information to the cpl.log
file that can be useful if you can’t tell what component is aborting the run, or where bad coupling fields are originating.
Try rebuilding and rerunning with the variable DEBUG set to TRUE (This ** requires rebuilding**):
./xmlchange DEBUG=TRUE.
This adds various runtime checks that trap conditions such as out-of-bounds array indexing, divide by 0, and other floating point exceptions. Before running, you must rebuild the run:
./case.build --clean-all
qcmd -- ./case.build.
Note that the model will run significantly slower in DEBUG mode
, so this may not be feasible if the model has to run a long time before producing the error.