Traceback with IFC

[gfthomas8]

The User's Guide claims that one can generate run-time diagnostic reports via /d{n}.

So in the project properties pages dialog I specify

1. under Fortran/Diagnostics/Runtime Error Checking All
2. under Ccommand Line I enter d0, d{0}, and other variants in the Additional Options pane but

no joy. I'm trying to generate an integer overflow exception in a console application.

Anyone know how to do this?

Ciao,
Gerry T.

[Steven_L_Intel1]

IFC doesn't offer the ability to detect integer overflows. It would need to generate special code for that, and it doesn't.

IFC doesn't have traceback - what it does have is the ability to add code for certain run-time error checking, and then you use /d to specify what level of detail you want displayed.

Steve

[gfthomas8]

Now I get. Even though I had my glasses changed recently I didn't notice that checks are made depending on all/custom and that they are greyed which is just a shade lighter than ungreyed to my eyes.

When in the debugger a dialog pops up titled Fortran run-time error with the message

Deallocate error 492: variable is not allocated. End of diagnostics which on OK'ing causes the .NET 2003 to close or crash. How come? I don't get a diagnostic report.

Ciao,
Gerry T.

[Steven_L_Intel1]

I can reproduce this behavior (VS.NET exits) with 7.1. I have no idea why it happens. Please report this to Intel Premier Support.

Steve