# 2019 platform MOVESMRG segmentation error **URL:** \ **Category:** Run Errors and Warnings\ **Created:** [August 6, 2024, 9:00pm UTC](https://forum.cmascenter.org/t/2019-platform-movesmrg-segmentation-error/5137 "2024-08-06T21:00:44Z")\ **Posts on this page:** 1\ **Showing post:** 23
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [August 26, 2024, 3:06pm UTC](https://forum.cmascenter.org/t/2019-platform-movesmrg-segmentation-error/5137/23 "2024-08-26T15:06:29Z")
See [https://github.com/cjcoats/SMOKE-m3utilio](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 `INCLUDE`ing 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](https://forum.cmascenter.org/t/error-running-movesmerg-for-rpd/4606/4)) > have been fixed… This may be related to the seg-faults. --- _[View the full topic](https://forum.cmascenter.org/t/2019-platform-movesmrg-segmentation-error/5137)._