Model

Have a large Fortran system, have been debugging using 'step into' and run. All of a sudden, 'step into' does not work, when I do a build and 'step into', the system displays the screen that it is starting execution then I get nothing! I thought it was due to the size of the program but I ran a much smaller program and it did the same thing. I am wondering if anyone has ideas about why this is happening. A response will be appreciated. I also tried to just run, without the 'step into' command, just execute, seems to work fine Thanks, Sid Kraft

You will have to give more particulars (example program, compiler version, OS version).

I tested a simple console project with one file. After creating a new project in Plato (FTN95 8.1), I added an existing fixed format Fortran source file with the main program and one subroutine. I set the target to Debug-Win32, built the project and chose Build->Step Into. Plato opened the source in SDBG and everything looked fine. I stepped over a couple of source lines and watched the local variables change value.

Everything seemed OK!

mercej4: Not sure of all of the particulars but I removed the silverfrost module, downloaded the latest version on the website, completely deleted my existing project and re-built, same friking thing, when I try to build and 'step into' the system pretends to do, displays all of the entry screens, goes through all of the motions and then NOTHING!!!! I have done nothing other than changed some of the variables in one of the routines, did a re-build and tried to execute using the debug command 'step into', strange that all of a sudden the system quit working as it has even after downloading and re-building my system and even a smaller project file. My question to you is what do you need, my uploaded simple project file or? Do not know how you will replicate with your system as opposed to mine, very, very frustrating to say the least. Sid Kraft

mercej4 using Win 10, latest updates, Sid kraft

mercej4: Getting more frustrated by the minute, now with the new, downloaded Silverfrost, tried to create a new, simple fixed Fortran program and compile, now get the error FTN77 must be on the path, really think that I need a user manual for this system, I am a developer, not a system programmer, have never had so many problems in the past, most seem to be very simplistic but are driving me to drinking - ha!

There should be no need to have FTN77 at all. In fact, many of the FTN77 tools do not work (or not properly) in Windows 10.

Assuming that you have FTN95 Version 8.1 on Windows 10, please do the following, and take notes on what you observe, especially about unexpected problems and error messages.

1. Open a command window and run the <FTN95 directory>\fvars.bat. This will set up the path to the compiler and tools.

2. Type the command 'Plato'. This will open the Plato IDE.

3. Create a new console EXE project, and add your source file to the project. Choose Win32-debug as the current target configuration and build.

4. Choose Build->Step Into (F7). Step over a few lines of source code.

Report your observations before you resort to drink.

mercj4: Did everything you suggested, in detail, went to compile and build, system responded 'FTN77 Not On Path' ??????? what the heck does this mean? Sid Kraft

You may have some old settings from years ago. See if the hints in this old thread help.

https://forums.silverfrost.com/Forum/Topic/2283

Do you have FTN77 installed now? Did you, previously?

Plato does allow you to use FTN77 in place of FTN95 but FTN95 is the default Fortran compiler used by Plato.

Open up the 'Options' dialog from the 'Tools' menu and find the check box that relates to using FTN77 in place of FTN95 and switch this off.

Paul: I looked at some of the previous comments, thanks to mercej4, and issued the command in 'options' use FTN95 rather than FTN77, got around the problem with the path selection. However, I am still plagued with the problem where the 'step into' command produces nothing!! when I issue it, it goes through all of the commands as if it is going to work and then, no output prompting. Interesting that when I deleted the Silverfrost program, installed a new downloaded copy and executed, the first time it displayed the tip screen, when I deleted, the 'step into' command worked one time. When I came back to do again, it would not work, any ideas on this? Sid Kraft

Sid,

I don't know what is going wrong but I suggest that you run SDBG.exe directly, either from a command line or from Windows File Explorer. From a command line you type 'SDBG prog.exe' where prog.exe is the name of your executable.

Paul: Is there a way that once one starts and execution, i.e. 'step into' and the system does not perform correctly to stop execution and return to Plato to redo another build and execute without stopping Plato totally and re-start? With this current problem of executing the 'step into' command which does not work, I am continually having to exit Plato and re-start, frustrating to say the least being I am unable to get the 'step into' command to work? Sid Kraft

Paul: Certainly cannot believe that all of a sudden having so much trouble getting the 'step into' command to work. I tried to execute, at your suggestion, by running the module directly from the command line, it runs the program but I have no way of 'stepping into' the debugger, what the heck is wrong with this system? I removed the Silverfrost program from my win 10 computer, completely downloaded and rebuilt, re-built my Project file and still experiencing the problem. This problem is not only not working with my large program but also with a single line Fortran program, 5 line of code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Something drastically wrong but not sure what! What info do you need to help solve the problem? Sid Kraft

Paul: I surely do not want to migrate all of my Fortran programs to another system as the Silver Frost support has been so good too date. However, do you know of another Fortran system that I can use being I cannot get the solution to this trivial problem that I have? I suspect it has something to do with my using Win 10 as I have had problems in the past with Silver frost and Win 10. I cannot continue to use my program without a debug facility, there is no way to step through the program and get the results of debugging needed. What a shame as the Silverfrost system is superior to anything I have seen. Anyway, any help will be appreciated, Sid Kraft

Paul and mecej4: As I suspected, the problem that I am having is a problem with running programs under win 10 with Silverfrost, I re-loaded Win 7 and all works fine. For future reference, win 10 and Silverfrost are a poor mix for anyone using the system. I am uterly shocked and surprised that you guys are still having problems with the Win 10 op sys and Silverfrost, if I can be of any help, let me know, I will upload whatever fortran programs that I have although, it is not with my Fortran system it is a conflict between win 10 and Silverfrsot. As I explained, after using the system several times, all of a sudden, the debug, 'step into' proces ceases to function, goes through the motions and then provides no cvommunication to the user. Sid Kraft

Sid, I have used FTN95 extensively with Windows 10 (64 bit), both the Home and Prof. versions. I have not experienced the problems that you touch upon.

Let us keep things simple. Take any Fortran program, and compile and link it at the command line with the /debug option. Then, run SDBG.EXE and tell it to load the EXE that was built from your program. Note that Plato is not involved in this. Next, try stepping over a few lines of your program.

What do you observe?

Sid,

As a possible alternative approach. I have had problems with some of the local windows within SDBG becoming lost, as their screen address becomes corrupt and is not on the visible screen dimensions. Could your problem be related to not being able to see the response screen ? I think I deleted sdbg.ini and tried again, although this was with an older version of sdbg. Also check for virtual copies of sdbg.ini as I have also had problems with system protection of this file.

Having no any additional problem with Win10 besides being hacked recently (Win10 own antivirus and antispyware misses bugs. Check for viruses using other programs). So this is not much help probably. Besides, though Plato probably became recently very usable and many switch on it, i traditionally compile using tricky command BAT files, use own editor and call debugger directly, not via Plato.

During using win 10 and Plato, when I run using 'step into' system shows a yellow arrow at each line number and have to click on 'step into' again to move down a line. Is there a option to 'step into' and then click on run to get the debugger to advance one line? Also, John Campbell suggesting erasing sdbg.ini and try again, where is it located and if I erase, will it automatically be restored? Sid Kraft

You should be able to 'step into' (meaning into the first function/subroutine call on the current line) or 'step over' (meaning don't step into but advance to the next line of code). If this doesn't work for you then try running SDBG independently of Plato. You can do this by starting SDBG from a command line or by changing the Plato options from the 'Options' dialog on the 'Tools' menu.

I suggest that you search for sdbg.ini using the Windows Explorer application. It is safe to delete any ini file with this name that you find.