-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
garbage binary in log files when Y/N env var is set to ' ' #81
Comments
Training data package with SMOKE 5.0 executables |
Garbage binary also found in smoke report files. e.g. $REP_ROOT/inv/rep_rwc_2018gg_18j_inv_state.txt |
No garbage found in smkinven_rwc_2018gg_18j.log if SMOKE was compiled with gfortran. However, there was array out-of-bound issue in variable OUTDNAM( RPT_%NUMDATA, RCNT ) occurred in subroutine WRREPHDR (src/smqa/wrrephdr.f) when SMOKE was compiled with gfortran. When SMOKE is compiled with gfortran, segmentation fault occurred and point back to this error
Code snip set with new line inserted for debuging:
Such error did not occur if SMOKE was compiled with ifort, which just assign garbage value to OUTDNAME untill it is filled
|
Update: ifortran would pick up out-of-bound error if SMOKE was compiled with "-check bounds" flag.
|
Fixed by modified $IOAPI_HOME/ioapi/m3err.F Original code block:
Modified code block:
Re-compile both IOAPI and SMOKE to take the fix into effect. |
And probably coming from C programmer who does not know how to correctly interface with Fortran, in spite of the fact that there are numerous examples of that in the I/O API ;-( NOTE: |
Noticed this in some of the log files created from the training data package. Some of the log files have binary data which means grep needs the "-a" flag to work.
grep ARINV smkinven_rwc_2018gg_18j.log
Binary file smkinven_rwc_2018gg_18j.log matches
grep -a ARINV smkinven_rwc_2018gg_18j.log
File "ARINV" opened for input on unit: 98
Looking at the file in vi, the binary characters show up when a setting read with ENVYN is ' ':
Need to check the version of the I/O API in use
The text was updated successfully, but these errors were encountered: