Dear Wien2k mailing list,
there is a small bug in tetra -enefile which could occasionally result
in a crash like this:
x tetra -enefile
Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.
Backtrace for this error:
Segmentation fault (core dumped)
0.023u 0.389s 0:00.56
On Wed, 2018-07-11 at 11:21 +0200, Peter Blaha wrote:
> I've been able to reproduce the problem with gfortran, and also made
> a
> fix, which according to my tests seems to work.
>
> Please try the attached jacdavblock.F file.
>
> This fix is not necessary if ifort is used, but should not harm
I've been able to reproduce the problem with gfortran, and also made a
fix, which according to my tests seems to work.
Please try the attached jacdavblock.F file.
This fix is not necessary if ifort is used, but should not harm either.
Regards
On 07/10/2018 02:11 PM, Pavel Ondračka wrote:
Dear Wien2k mailing,
so I noticed that the old crash with -it (with gfortran only of course)
is still present in the 18.1 version:
At line 140 of file jacdavblock_tmp_.F (unit = 200, file =
'./case.storeHinv_1_proc_0')
Fortran runtime error: Sequential READ or WRITE not allowed after EOF
marker,
4 matches
Mail list logo