breakpoint shifts to a write statement in VS2005

[xinxu]

I have just installed Visual studio 2005& IVF 10.1 on my PC with Vista Ultimate SP1 64bit. I have also installed the SP1 for visual studio and the visual studio update for vista. When I try my Fortran programs, I found that the break points changes position in the code. After trial and errors, I found it happens even for a simple program.

I can reproduce it on my PC by writing asimple program and set the target platform to x64 and the configuration to x64, my break points in the program willchange to a location where a write statement is. The following isthe sample code:

1 Program main2   print *, "This breakpoint shifts down."3   write(*, '(i1)') 14   print *, "This breakpoint does not move."
5 end program

If I set a break point at the 2nd line and debug the code, the break point will shift to the write statement and the program will pause there. If I set the break point to the 4th line and debug the code, everything looks fine. All breakpoint works for the win32 configuration. Here is the installed products on visual studio:

----------These are copied from vs help->about ----------

Microsoft Visual Studio 2005
Version 8.0.50727.867 (vsvista.050727-8600)
Microsoft .NET Framework
Version 2.0.50727 SP1

Installed Edition: Professional

Microsoft Visual Basic ... C#... C++ ...J#... Web Developer... Web Application Projects ...Crystal Reports (details areommitedhere)

Intel Fortran Compiler Integration
Intel Fortran Compiler Integration for Microsoft Visual Studio 2005, 10.1.3948.2005, Copyright (C) 2002-2007 Intel Corporation

Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1 (KB926601)
This service pack is for Microsoft Visual Studio 2005 Professional Edition - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/926601

Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB937061)
This Security Update is for Microsoft Visual Studio 2005 Professional Edition - ENU.
If you later install a more recent service pack, this Security Update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/937061

Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB932232)
This Update is for Microsoft Visual Studio 2005 Professional Edition - ENU.
If you later install a more recent service pack, this Update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/932232

Is there anything I have missed?

Thanks & Regards,

Xin

[xinxu]

Update

If I change "project properties->Fortran->Debuffing->Debug Information Format" from 'Full' to 'Line Numbers Only', then the breakpoints will not shift locations.

[Steven_L_Intel1]

I can't tell which specific update of 10.1 you installed - unfortunately, the About information you posted does not identify it. You should have 10.1.021 installed - some earlier versions had problems like this.

[xinxu]

Thanks Steve for your reply!

I checked my compiler version. It is an old version 10.1.014. So I downloaed 10.1.021.

1) uninstalled 10.1.014 integration and compilers for 32 and 64 bit and the debuger 10.1.

2) installed 10.1.021 (my old license file is not valide for this update. So I applied for an evaluation license key)

Try my program and the simple test program pasted above. Same behavior of the debuger is observed! Is there anything wrong with my installation?

[xinxu]

I have just finished a fresh install of Vista Ultimate 64, visual studio 2005 and IVF 10.1.021 (evaluation license).

The debuger is still not working properly. I mean the above problem still appears.

Any ideas on that please!

[Steven_L_Intel1]

I will see if I can reproduce this. Do you see a problem debugging other programs?

[xinxu]

I have seen the problem when I am working with my own programs. I have also seen the problem on my friends programs.

I have got the problem partly solved by uninstalling the latest IVF 10.1.021 and install an earlier version IVF 10.0.026. I did this because I found this version works on one of our PCs in our office. I don't know what the problems is and why the old version works.

However, when I use call stack to traceback the calling procedure, the debuger will point to the next line of the code instead of the line it is surposed to point to.Since this is not a big issue, I'd better use it for now and focus on my work.

I believe this is reproducable because I have found the problem on five 64-bit PCs in our office. This is also the issue that preventing us from using the latest version of IVF.

[Steven_L_Intel1]

I'm sorry that I have not had a chance to look at this. Please submit a problem report to Intel Premier Support and attach a test case - it will be investigated.

[cmmaslin]

I have the same problem too. I'm using Intel Fortran 10.1.4156.2005. I cannot place a breakpoint anywhere before the first write statement in a subroutine, as it always moves to the write statement. Debugging after the write statement is fine.

[Steven_L_Intel1]

Please report the problem to support.

[Kevin_D_Intel]

I reproduced the behavior Xin reported using VS2005 SP1 (Standard Edition) with IVF 10.1.019 on Win2003 Enterprise x64 Edition. I also verified the work-around of generating debug information for 'Line Numbers Only'.

This is unique to the x64 configuration. I will send the issue to the appropriate compiler development team and post an update with new information as I learn it.

[Kevin_D_Intel]

The latest 10.1.024 update contains a fix for this issue.