/fpp interferes with breakpoints/stepping through code

[cisteefel]

I have been having problems with Microsoft Visual Studio .NET 2003 combined with Intel Visual Fortran 8.1 since I moved to a new laptop (Windows XP, Core 2 Du). New install of all the software (MVS and IVF) and my application compiles and runs properly. But I can't set breakpoints that don't appear as question marks when the code starts to run in debug mode. This worked properly on my old laptop (Windows XP, Pentium 4 single processor).

Decided to make a simple Fortran Hello World Program. When I compile with default options, no problem of course to step through the code. But when I use /fpp (needed for my larger application), the breakpoints don't work. I read elsewhere that IVF 8.X had some problems with adding extra lines here (I don't have any now that begin with #, at least in the Hello World code). Somebody mentioned stripping these out, but I haven't been able to find this option in the User's Manual.

I am in the process of upgrading to IVF 10.0, but in the meantime, is there any way to fix this. Still don't understand why it would have worked on the older machine and not here.

[cisteefel]

Just did a simple test. Deleted the Hello World project just to make sure, made a new one with just a write and read statement. Compiled on my Core2 Duo (Windows XP Professional) using 100% default options and the stepping through the code and the breakpoints work. Invoking /fpp gives me the same problem--no source code available at the breakpoint. My old machine, a Pentium 4 running Windows XP Professional, in contrast, works with debugging both ways (with and without /fpp).

So there is either something about the chip set here, or there is some subtle difference in the installation (Microsoft Visual Studio .NET 2003, followed by Intel Visual C++ 8.1 and then Intel Visual Fortran 8.1). Or some other Environmental Variable affecting things??

[Steven_L_Intel1]

I can't explain the behavior differences you're seeing. I know that in the past the compiler sometimes had trouble assigning debug line numbers in preprocessed source - that is not something you can "fix" other than upgrading. But why the same build would work on one PC and not another, I can't figure out.

The symptoms you describe suggest to me that perhaps the project file paths are such that they are not valid on the new system. Do you have explicit file paths with device letters in places such as the linker output or debug target?

[cisteefel]

I agree--very mysterious.

I have done the paths both ways, with explicit file paths (e.g., C:Documents and Settings...) and with relative, as would be the default just starting up a Visual Fortran project.

It wouldn't have something to do with the treatment of the temporary files (put in some place like Local Settings/Temp/blah blah...??

I will try the non-working executable on my old laptop to see if I get the same problem. That would give some information as to whether the problem was with the build, or with the OS set up...

[Steven_L_Intel1]

Temporary files ought not to be an issue.

[jimdempseyatthecove]

I too rely heavily on /fpp.

V8.x did have major problems. By V9.1 the problems were mostly fixed. Occasionaly I get a few hiccoughs but not all that often.

Time for an upgrade.

Also note. During various upgrades of IVF I noticed some FPP problems that were solvable by copying an older version of FPP into PATH. Perhaps your notebook is compiling OK using an older version of FPP.

Jim Dempsey

[cisteefel]

I only see one version of fpp.exe on my machine.

One possibility is that I have a slightly upgraded version of 8.1X on my older machine--I will check that tonight. The version I have my new machine does seem to be prior to the fixes.

Otherwise, I agree on the upgrade. Just ordered it now. This is always money well spent, since my time for a day of work (or a day searching for a solution) exceeds by far the cost of the compiler.

[cisteefel]

I am trying out an evaluation copy of IVF 10.0, but the instructions tell me to uninstall Microsoft Visual Studio. When I go to uninstall, the only option is a new install. Unbelievable, who needs computer viruses with Microsoft out there...

[cisteefel]

OK, I guess I still need Microsoft Visual Studio .NET 2003--good thing the uninstall did not work. I thought that IVF 10.0 came bundled with Microsoft Visual Studio 2005??

Anyway, IVF 10.0 fixes the problem. Evidently my older laptop has a slightly upgraded IVF 8.1 that must have fixed the problem. I must have downloaded the fixes, which are now unavailable as far as I can tell. But an installation of the older 8.1.0X must have still had the bugs in there.

[Steven_L_Intel1]

If you purchase IVF 10, you get the necessary Visual Studio, but because we pay royalties to MS we can't offer this in free evaluation copies. I thought this was made clear on our web site, but you're only the umpty-thousanth user to complain about the same thing, so I guess we need to figure out how to say it better.

[cisteefel]

It was clear once I read the Installation Guide. I have a tendency not to read all the fine print otherwise. Usually this stuff is buried with the System Requirements that one needs 500 MB RAM etc, which I tend to ignore (who would buy a computer with less, or who would sell one with less)...

I checked and my working copy is IVF 8.1.238, while the non-working one was 8.1.018, so that apparently explains it. Somehow I upgraded the original 8.1.018 installation that I had purchased, and then conveniently forgot about it.

[jimdempseyatthecove]

You could copy FPP.EXE from the notebook to the desktop as a work around untl you get V10 working. As long as you are a single developer it should fall within the scope of (spirit of) your license.

Jim Dempsey

(not and Intel employee)

[cisteefel]

Version 10 is working now, except for the selection of various Project attributes (optimization) etc.

But wish I had thought of this earlier...

[Steven_L_Intel1]

It is unlikely that FPP itself was the problem, but it's possible.

Please report whatever problems you are having with project options to Intel Premier Support.