CVF 6.6C crash and freeze

[Nick2]

Is it just me...

With a certain project that I work with on CVF 6.6C, while I'm stepping through the code, if I set too many data breakpoints (I think) the development environment will crash. (GPF. Remember those?) If I'm stepping through the code, my machine will randomly freeze for a random amount of time; ie. it takes about 30 seconds to re-draw a window that I click on. The freeze just as randomly goes away (after I F5 the code to the next breakpoint, sometimes I have to F5 it more than once for the problem to go away), and goes away if Iexit the development environment via pressing the PC power-off button. I have an up-to-date computer, and my coworkers have the same problem...

Has anyone else experienced these kinds of problems?

[Dishaw__Jim]

I haven't used CVF in a quite some time, however, I have experienced freezing while using the Intel Debugger. It seems to occur when I have an "array operation." For example,

REAL, ALLOCATABLE :: my_big_array(:)

ALLOCATE(my_big_array(8192))

my_big_array = 47


When I attempt to step through "my_big_array = 47" the debugger becomes nonresponsive, i.e. if you press F10 to step, the debugger does not go to the next line of code (instead I think the File menu opens up). After some interval, the debugger is working fine. The interesting point is that if I have a breakpoint at the line immediately after "my_big_array = 47" and pressed continue (F5) before "my_big_array = 47", there is never a delay. The delay only seems to occur randomly when stepping.

[Steven_L_Intel1]

James, the issue you're seeing has to do with the way the debugger steps over the statement. Your array assignment has lots of instructions, and the debugger may be single-stepping through them. I thimk this is something we improved within the past year.

[Dishaw__Jim]

That was my guess. What I found unusual was that the amount of time spent was not constant for a given instruction. I guess it is time to download and install the latest.