On 21/07/2019 19:44, Steven Franke via wsjt-devel wrote:
On Jul 21, 2019, at 12:58 PM, John Nelson via
wsjt-devel<[email protected]> wrote:
Hi Bill,
I managed to get someone to run the code from a Terminal window. It exits with:
“At line 1 of file /Users/bill/wsjtx-prefix/src/lib/gen65.f90
Fortran runtime error: Actual string length is shorter than the declared on for
dummy argument ‘msgsent’ (-216172782113783786/22)”
— John G4KLA_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi John,
I’ve lost track of which issue your report pertains to. It seems that there are
3 possibly unrelated issues at play on MacOS.
1. Crash related to reading the LoTW user file. Bill has identified the cause
of this problem.
2. Kevin, VE7DS’s report of a crash related to MSK144 mode. I have tried, but
have not yet been able to reproduce this here.
3. George, KF2T’s report of a crash on startup when running a beta version of
MacOS. I have not tried to reproduce this.
Which one does your report address? Or is your report yet another problem?
Steve k9an
Hi Steve,
it looks like there's a common thread emerging with strings passed
between C++ and Fortran. I squashed one of these before the release but
it seems there are others. I think it is related to a Fortran compiler
upgrade on my build machine. The problem is almost certainly that some
of our code is using techniques for passing C strings to Fortran that
are not guaranteed to be well defined and the later versions of gfortran
are not assuming that those techniques should work. I do have a
background branch in progress to move all C++/Fortran boundary crossing
code to more robust use of ISO_C_BINDING, I guess that will have to be
promoted to a higher priority.
73
Bill
G4WS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
