forums.silverfrost.com

DanRRight · Posted: Tue Jul 30, 2024 5:50 am Post subject: On 9.03 update

I installed this update and got the following issues:

1) Run time error: call to missing routine __return_pstach_ptr
The debugger points on error on completely legitimate line. In one crash cases the error was in the first line of the first function after CONTAINS keyword in module.

I added some other dump function before this function like this

PaulLaidler · Posted: Tue Jul 30, 2024 7:25 am Post subject:

This release of FTN95 requires matching DLLs with the same date. They can be downloaded from the same place.

DanRRight · Posted: Tue Jul 30, 2024 8:23 am Post subject:

Same date May 14, same Support place above

JohnCampbell · Joined: 16 Feb 2006 Posts: 2615 Location: Sydney

My Version of FTN95/x64 v9.03.0.0 is time stamped 18/05/2024, although this may be the timestamp I downloaded the 8 files I updated.

My recent files are:

DanRRight · Posted: Mon Aug 05, 2024 10:48 pm Post subject:

John, Where have you downloaded it from? From here above or from personal support contract website?

JohnCampbell · Joined: 16 Feb 2006 Posts: 2615 Location: Sydney

Dan,

I downloaded from here (the support thread), but there might be a problem with your other .dll's ?

DanRRight · Posted: Sat Oct 26, 2024 1:53 am Post subject:

903 did not work for me so i returned to 902. But it got me unexplained errors recently in CLEARWIN64.DLL couple of which required to corner them for a week, one is still not resolved. Other appeared no one knows how and disappeared similarly after a week of tries

Tried september's 904 and returned back to 902. The 904 just crashes in the middle of compilation and other programs compile but still do not start because of missing __return_pstach_ptr. The handymen/workarounders here who never report any problems or suggested a single improvement or change in decades would particularly like compiler itself (not the program) crash report:

When fail to find the workaround they will just wait someone else will report it. By the way many other programmers even do not know what is Access Violation, never exhibited them in MATLAB for example. Because millions of active users is there doing serious work. I had 50 per day last week

PaulLaidler · Posted: Sat Oct 26, 2024 7:08 am Post subject:

Dan

As far as I know there are no issues of this kind with v9.05.

The v9.05 download includes FTN95, SLINK64 and the DLLs so the problems that you have had because you used a new FTN95 with old DLLs should not happen with v9.05.

JohnCampbell · Joined: 16 Feb 2006 Posts: 2615 Location: Sydney

Dan,

I had problems with (drectly) running programs compiled with /check.

However if i used "SDBG64 program.exe", this helped identify any errors. This may help in your case ?
I am not sure if this can overcome any apparent incompatibilities you may be identifying.

DanRRight · Posted: Sat Oct 26, 2024 11:00 am Post subject:

Paul,
Sorry i mistyped 9.04 but actually 11 Sep 2024 update I used was 9.05. May be this update is more stable but i can not see how it handles my program crashes because this time my programs crash the compiler itself Wink

. First and second picture above are about 9.05. Rest of pictures are about 9.02

Besides, some other my programs also do not run with 9.05 because it is still missing something like __return_pstach_ptr I do not know what it comes from (Fig.2 above)

John,
I always use SDBG64 and directly run only programs compiled with /NOCHECK. By the way typing "SDBG64 Program.exe" or "SDBG Program.exe" is the same, SDBG/SDBG64 recognize 32/64 bit programs automatically

PaulLaidler · Posted: Sat Oct 26, 2024 12:55 pm Post subject:

__return_pstack_ptr may be called by programs compiled with FTN95 /64.

This function is located in any clearwin64.dll built after 10 April 2024.

If it is missing when you run your application then you must be accessing a clearwin64.dll that was built before this date.

Search your computer to find out where your DLLs are located and which versions are currently being accessed.

DanRRight · Posted: Sat Oct 26, 2024 1:24 pm Post subject:

Now compiler distinguish cap/noncap letters ?

PaulLaidler · Posted: Sat Oct 26, 2024 4:57 pm Post subject:

No it makes no difference.

You need to find a way to ensure that the latest clearwin64.dll is the one that is accessed by your application.

There are various ways to do this. You could rename the ones that you don't want to use. This is better than deleting them in case you need to backtrack.

DanRRight · Posted: Sat Oct 26, 2024 10:32 pm Post subject:

Paul,
If someone here wants to see one of images of devilry it is above just in front of your eyes on the green field. This is of the same sort of things how due to quality control issue USA lost the Venus planet space race to USSR when just one single letter in the Fortran source code caused Mariner 1 to crash.
Same multiyear problem we had before with the older DLLs in the path.

Anyway, after cleaning this devilry the other codes compile and run OK but one code still crash the compiler. This is latest pic for this if this tells you anything

JohnCampbell · Joined: 16 Feb 2006 Posts: 2615 Location: Sydney

Dan,

show us the results of:
Runtime error from program:c:\program files (x86)\silverfrost\ftn95_905\ftn95.exe

(after you rebuild all binaries with the revised FTN95 compiler path settings !)

If you are doing this path update, also make sure that you update any toolbar links to the correct path (expecially for plato and sdbg64)