Break on variable value changing

[ferrad01]

I thought I'd post this again to see if it has been fixed in v10 of the compiler.

Ever since I moved from Salford to the MSPS ->DVF -> CVF -> IVF range, I have never been able to reliably break on the change of value of a variable. It has been hit and miss (in Salford it was 100% reliable), most of the time it does not work. The main problem is that, once such a break point is set, and F5 is used to resume running, the system slows to almost a complete standstill. At other times, it just does not stop even if the value changes

This problem still exists in v9, I was wodering (hoping) that it had been fixed in v10? Salford managed it 20 years ago...

[Steven_L_Intel1]

This is really dependent on the MS debugger - its implementation of data breakpoints has never been very good. The compiler has nothing to do with it.

[ferrad01]

Can you clarify? I thought that the IVF environment would implement debugging - why is the MS debugger used? Which MS debugger? I hope you're not saying you're still using the PowerStation debugger?

[Steven_L_Intel1]

When you are debugging in Visual Studio, you are using the Visual Studio debugger which has been enhanced (with a DLL that is provided by us) to understand Fortran. Basic functionality such as breakpoints is handled by the VS debugger, which calls IVF code when it needs to understand a variable name or expression you type, but once it identifies an address to be watched, it uses generic code to do that and IVF is not in the picture.