2019 platform MOVESMRG segmentation error

SMOKE Run Errors and Warnings
23

See https://github.com/cjcoats/SMOKE-m3utilio:

Last year, while I was recovering from a hip replacement, I kept busy by doing a then-SMOKE re-write where I did a number of clean-ups that should have been done long ago:

  • USE M3UTILIO instead of INCLUDEing 20-years-obsolete ioapi/PARMS3.EXT etc., which provides subroutine-argument checks for almost all the I/O API routines, and which also ameliorates the problems that come from SMOKE’s use of non-Standard “fixed-132” source-format;
  • Fixed a number of numerical problems;
  • added a lot of additional error-checking; and
  • converted the source to Standard-conforming “free” source format.

Unfortunately, the latest SMOKE release did not take advantage of this work (which was done as a gift to the community, purely on my own time, and outside of any EPA nor university funding).

Among the subroutine-argument errors found by the USE M3UTILIO were:

Argument-list bugs that were found, as well as the FORMAT bugs in
src/movesmrg/rdmrclist and lib/efsetup (MCREFIDX and VOLNAM are
CHARACTER, not INTEGER as FORMAT 94010 demands; see
Error running movesmerg for RPD - #4 by cjcoats)
have been fixed…

This may be related to the seg-faults.

1 Like