Bug or newbie error??? (Page 1 of 2)

Don,

What call are you using to retrieve the filename from the command line?  I'm not sure why you'd see the filename repeated over and over again.

Don,

Are you seeing something like the following?

The debugger is actually saying that it found your filename followed by 234 spaces.  Note that the actual structure of the value is:

'1hrTime IntErosion.WDC',' ' <repeats 234 times>

In the value above, your filename is correctly read, and it is surrounded by single quotes as reported by the debugger.  The debugger goes on to say that, after your filename, there appears to be 234 space.  After the comma, a single space appears in single quotes, and that is all that is being repeated.

The spaces are repeated because Fortran doesn't really have a way to mark the end of a string.  Usually, though, it uses spaces to fill in the unused portion of a string.  The Compaq debugger may have stripped the information about trailing spaces when reporting the value.

When I print the value of image while debugging, I do get the proper filename.

Addendum:

I moved the file to the project directory.  It found it without problems.  So, now I'm wondering why....
Don

I'll give it a try.  Might be awhile, tho.  Other things pressing.
Don

Addendum:  Just tried to debug and it appears to work - at least it took me to my first breakpoint.

Jeff,
There wasn't an error code - just the message. I didn't select either console, so I guess it was the default.  What is the difference?
Don

Don,

Using the internal console (default) or the external console leads to the program being launched in slightly different ways.  I was just wondering where to start looking for a bug.  I'll have a look at the internal console code.

The informational warning you're seeing, (and it's not an error, just information) means that a number was calculated that was, in absolute value terms, so small that it could not be represented by the standard floating point values due to the magnitude of its exponent.  Again, the message is informational.  You should be able to disable it using:

-ffpe-trap=none

in your Fortran compiler flags (accessible via "Options..." in the Project menu, then click the "Compiler Flags" tag).

Don,

I apologize for my last post.  What you actually want is:

-ffpe-summary=none

That should suppress the runtime warning.

You should be able to view variables in a derived type exactly as you've stated.  If these aren't working in watch statements, it is a bug.  One note, though, is that you can't currently view the internals of allocated arrays.  Are you having trouble viewing members of a derived type?

You can view the value of any variable or expression by highlighting it and then hovering your mouse over the highlighted text.  By allowing highlighting, you can quickly view expressions rather than just variables.

Don,

When debugging, the debugger should stop at the first executable Fortran statement, which might be what you're seeing.  You can disable this by opening Debugger Options from the Options menu and unchecking "Break on Start."

I'll have to look into what's wrong with viewing derived types in the debugger.  I had thought everything was working well with them.

Jeff,
I told you wrong before.  It appears to ignoring the entered working directory entirely.  I had a copy of the input file in the .exe directory and that was where it was picking it up and storing the output.
Don

Both these symptoms suggest to me that your working directory does not exist, or at least Simply Fortran cannot find it.  It could be that there is a minor typo in your working directory or a bug exists.  The debugger will actually launch fine and throw an internal error when the directory is not found, but it will proceed with the debugging session.  I'm adding some code now that will warn users if the directory does not exist at the time of launch.

Still looking into it.

It's not that Compaq and Simply Fortran use different tab characters.  Simply Fortran is actually enforcing the standard that no tabs be allowed whereas Compaq allowed them for some reason.  A bulk replace is not possible with Simply Fortran or the tools included.  You could do so with Windows batch files; a Google search turns up some answers.  However, if your code is fixed-format Fortran, and the first tab character indents 7 spaces while subsequent tabs indent a different amount, you'll need a more elaborate replacement scheme than what Windows batch could provide.  I would personally try using a scripting language to do so (Python, Perl, etc.).

Thanks, Jeff.  I think I'm starting to get the hang of it now.  Now for one I think may be a compiler problem.

When I build my project in 64-bit mode, both run and debug go through to completion. However, when I use 32-bit, the debug runs to completion but the run version blows up. In essence, two calculated values are supposed to converge within a given limit.  If they don't converge within 100 iterations, the program considers it a fatal error, prints a message and quits.

The reason I think it's a compiler error is because a friend of mine is a CIS professor at KSU and he gets the same results using Eclipse.  Have you had this happen before?

Don