Breakpoint for array-bound errors

[jeffrey_t_b]

I am using the IVF 8.1.029 (Win32), with Visual Studio 2003. (Sidenote: The "about" dialog box in VS says that my fortran version number is 8.1.2613.2003, which is a bit odd.) When I compile and run a debug version of a program, IVF will (quite properly) throw an error if an array bound is exceeded.

Unfortunately, when this occurs in the debugger, the program stops at some weird location (output.c, part of the C runtime library, I believe). The call stack window doesn't even show any of my routines. I can't see which line contained the offending code. It would be REALLY NICE if the breakpoint would occur in the code that caused the problem, rather than some irrelevant C-runtime code.

CVF did this, and I assume that IVF can, too, but I don't what setting needs to be changed for it to occur. Anyone know which toggle to flip?

[Steven_L_Intel1]

I don't know the answer to this - I've seen the behavior as well. I suggest reporting it as a bug to Premier Support.

[hansr]

jeffrey_t_b,

have you reported this bug to Premier Support? Would you tell us the number? I'm very interested in a solution.

Regards

Hans

[jeffrey_t_b]

I did report it to Premiere Support. The issue number is 295893. Kevin Davis of the compiler support group responded (quite promptly, to his and Intel's credit), and duplicated the problem. I've attached the text of his response below. The issue status is currently "escalated", if that means anything. I hope that it can be fixed soon, as the problem makes debugging (my company's style of) code more difficult.

Dear Jeffery,

Thank you for contacting us about the debugging issue regarding the location of the actual breakpoint involving an out of bounds array reference.

First, the IVF version you find under the IDE signifies the version of our IVF IDE integration components not the actual compiler release. Yes, it can admittedly seem a bit confusing or odd.

Second, regarding the debugging issue, I believe I re-created this. What I see at the point of exceeding the array bounds reference with my test source is, the exception is noted, break indicated, then the source pain displays source for output.c and my call stack is as shown below:

ntdll.dll!77f43847()
abounds.exe!_for__issue_diagnostic() + 0x2eb
> abounds.exe!_output( =, =, =) Line 405 + 0x17 C
abounds.exe!vsprintf( string=, format=, ap=) Line 101 + 0x11 C
abounds.exe!_for_emit_diagnostic() + 0x3d

I am fairly certain this is likely what you are seeing. There is nothing that I judge you are doing incorrectly and unfortunately I do not have a work-around under the IDE for this. This appears to be an issue with our own MS.NET debugger integration component shipped with IVF.

If you run your Debug executable from a Cmd window you are likely to see the traceback information for the out of bounds reference similar to that shown below. Perhaps this may offer at least some form of a work-around until we can address this issue.

[snip]

I will report this issue to our debugger component Development team and keep you posted on the status.

Thank you again for contacting us about this issue and apologize for the inconvenience resulting from this.

Kevin Davis
Intel Compiler Support