You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check the dftb_out.log it will show bellow error at the end.
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 10 RUNNING AT 0e928b6d4c7f
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
But
If Execute dftb+ manually it is not giving any Segmentation fault. Example:
Describe the bug
When executing dftb+ inside a docker container using
docker run
command we are gettingSegmentation fault
To Reproduce
But
Segmentation fault
. Example:And inside the container execute
mpirun -np 4 dftb+ >dftb_out.log
Segmentation fault
Note:
All the inputs are same for both manual and automatic execution in docker container.
Expected behaviour
No
Segmentation fault
should be there while automatically executing inside docker container using Docker run command.Additional context
In the docker Image, bellow packages are installed.
And OMP_NUM_THREADS is set as 1 inside the docker container.
The text was updated successfully, but these errors were encountered: