Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Problems in 9.0.028 update

lklawrie1
Beginner
1,218 Views

I tried the upgrade (IA32 subset), recompiled my entire source and

a) the compile time seems a lot slower.

b) the program crashed -- which it was not crashing with 025.

So, I've gone back to 025 for now. Yes, I can upload everything to the premier site, but will take some time.

Linda

0 Kudos
11 Replies
Steven_L_Intel1
Employee
1,218 Views
Linda,

That is a surprising result. Please do send us a test case and we'll be glad to look at it.
0 Kudos
lklawrie1
Beginner
1,218 Views
I will have to re-install it -- there's no way I can have both on and active at the same time is there?
Linda
0 Kudos
lklawrie1
Beginner
1,218 Views

Issue 344139 and files to reproduce problem has been submitted.

Linda

0 Kudos
Steven_L_Intel1
Employee
1,218 Views
If you wanted to keep both on the system, here's how to do it.

Install one. Make a copy of the 9.0IA32 folder and rename it to remind you of the version. Install the other.

To switch when using the IDE, you'll have to add the copy's folders (BIN, INCLUDE, LIB) to the paths in Tools..Options..Intel Fortran. From the command line, you would edit the copy's ifortvars.bat to reflect the new path and run it from a command prompt.
0 Kudos
lklawrie1
Beginner
1,218 Views

I can try that on keeping two on the system but not sure keeping .028 is worth the effort.

Not sure the support people have read the issue properly -- first response (and only so far) was that it compiled okay -- which I already knew. It's the crash in execution that worries me.

I tried recompiling in debug mode, got different line numbers and messages (insufficient virtual memory seems to be the most popular), and when i tried to run from the Dev Environment -- it says the server threw and exception -- but you can read the info in the Issue number for more details.

Linda

0 Kudos
Steven_L_Intel1
Employee
1,218 Views
Ok, I'll take a look as well.
0 Kudos
Intel_C_Intel
Employee
1,218 Views

it says the server threw and exception

This can sometimes happen if you are very unlucky in the installation process (mixing old and new versions for example), and you need to obtain some good dll's from another ivf installation or from premier support.

Lars Petter Endresen

0 Kudos
Steven_L_Intel1
Employee
1,218 Views
It can happen other ways too. The way I usually fix it is:

1. Uninstall the Intel integrations into VS.NET
2. Do a "repair" of the VS.NET install (from add/remove programs)
3. Reinstall the integrations

I have read reports of MSVC users seeing this too.
0 Kudos
Groundsel
Beginner
1,218 Views

I had hoped this might answer a similar query for me. I too got a message (with 9.0.029)when I tried to debug:

"Unable to start debugging

Server threw an exception

Unable to start ....exe"

I tried uninstalling everything Intel (with the exception of the extreme device drivers). That is, I uninstalled

TheVisual Fortran Compiler 9.0, the Array Visualizer, the Debugger and the Visual Fortran Compile 9.0 Integration with Visual Studio. Then I reinstalled the lot from the 9.0.029 IA32 package. Unfortunately,the server still throws an exception.

Perhaps the message box which came up when I was uninstalling the integration might shed some light. I will attach it here as a jpg image. Do you think installing an earlier release might be prudent?

Tom

0 Kudos
Steven_L_Intel1
Employee
1,218 Views
That message is not relevant. It's a bug in VS.NET that is harmless. Try the suggestion I made above - you missed the part about doing the reinstall/repair of VS.NET.
0 Kudos
Groundsel
Beginner
1,218 Views

Thank-you, Steve. That did work. Sorry I missed the "VS" implication in the instruction regarding the repair.

Anyway, my debug facility is back in business with the most recent upgrade. Much obliged.

Tom

0 Kudos
Reply