-
Notifications
You must be signed in to change notification settings - Fork 150
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
Fix ESP SegFaults with GCC #728
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes in src/type/molecule.f90
seem unrelated to the ESP fix. Can you provide a reproducer which fails with the previous setup?
I do not remember exactly on which machine I tested this code, but...
Under gdb:
BD.xyz is available here: https://gist.github.com/foxtran/2e56ea6577bebf055967416d572675c9 So, I fixed |
@awvwgk, ping? |
…ndex of array Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
@awvwgk, ping? |
I compiled xtb 6.5.1 with
cmake -H. -Bbuild -DCMAKE_BUILD_TYPE=Release
(GCC 8.5.0 was found, I did not notice that xtb was compiled with OpenMP support according tomake VERBOSE=1
output)And, then, I tried to compute ESP. Unfortunately, I got some SegFaults when runs were. In
Debug
mode, I got Fortran runtime errors sinceread_xyz
frommctc_io
returns allocatedlattice
with size 0 andpbc
with size 1. I rewrote molecule.f90 a little bit to avoid these issues.Then, in esp.f, I again got a Fortran runtime error:
It was due to a part of the routine for checking approximate computing ESP time had
espe(i)
wherei
exceedsnp
afterdo i=1,np
cycle. So, I just put the index to a reasonable value - 1.