Windows triggered a BP; corruption of heap..this may be due to the user pressing F12...

[pchidamb]

Hi: I am using IVF 11.0.72 in Vista 32 bit. My code snippet is here: 1: PROGRAM MAIN 2: call MAIN_PROGRAM 3: print *,'program completed succesfully' 4: stop 5: end 6: SUBROUTINE MAIN_PROGRAM 7: implicit none 8: integer i,j,k 9: i=10 10: j=20 11: k = i+j 12: return 13: end I set BP at line 9. Memory window looks like: 0x003A3748 ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe ee fe îþîþîþîþîþîþîþîþîþîþîþîþîþîþ 0x003A3764 ee fe ee fe ee fe ee fe ee fe.... Fortran Compile option: /nologo /debug:full /Od /fpp /I"C:\Program Files\Intel\Compiler\11.0\072\fortran\mkl\include" /I"C:\Program Files\VNI\imsl\fnl600\IA32\include\DLL" /I"C:\Program Files\VNI\imsl\fnl600\IA32\include\STATIC" /gen-interfaces /warn:interfaces /module:"Debug\\" /object:"Debug\\" /traceback /check:bounds /libs:static /threads /dbglibs /c Please help! Regards Praba

[Anonymous66]

I am not able to reproduce this issue with the latest version of the compiler. Is there a reason you need to use 11.0.72? If not, I would suggest moving to a more recent version.

[pchidamb]

Thanks for verifying this issue. I have no problem in moving to the latest version. Recently I started getting this error. I do have some strange coincidence: I got the windows update "Security update for MSFT Visual studio 2008 Service Pack 1 XML editor (KB2251487) on 4 Oct 2012. I tried invoking the above test program (with additional write statement) from command prompt: .... c:\Users\mudaliar\Praba\Projects\WaveguideAlloc>testf77.exe i,j,k = 10 20 30 program completed succesfully .... It looks to me that heap corruption message is only with Visual studio IDE. Am I making apple orange comparison?

[Anonymous66]

This could be related to the security patch. Do you get the error only for this program, or for any program in Visual Studio?

[pchidamb]

I am getting this message for both c++ & fortran files which were working fine earlier.

[Anonymous66]

This sounds like a Visual Studio problem. I would suggest contacting Microsoft support. You can also try reinstalling Visual Studio.