The breakpoint failed to bind

[JohnNichols]

Steve:

This comes from VS 2013 -- Latest Intel Fortran - I must be doing something stupid - but I cannot see what it is - debug is turned on

[Steven_L_Intel1]

I haven't seen that one before, but a quick Google search suggests that you need to make sure the executable has been rebuilt in a Debug configuration. It is not enough for "debug to be turned on". I'm wondering if many of your debug problems here are due to out-of-date builds - it would fit many of the symptoms you report.

In Visual Studio, select Tools > Options > Projects and Solutions > Build and Run. For "On Run, when projects are out of date", set it to "Always build" or "Prompt to build". This will make sure that you're always running the latest executable.

[mecej4]

With regard to the build process, "out-of-date" has the following meaning: If item A depends on B, and the time-stamps on A and B show that B is newer than A, then A is out-of-date and probably needs to be rebuilt or, in some cases, "touched". The resolution is the resolution in the file-time structure used by the Windows OS, which is tiny compared to a second, let alone a day.

[JohnNichols]

Steve:

I created a brand new console file and still get the error on the print statement - all attached.

I have debug switched on - I checked all the switches - I tried it with MAGNICSR that has not been touched for a year and debugged before -

also tried it on the home computer . Same errors -

I am using the latest Windows 10 build - it started after the last install.

John

[Steven_L_Intel1]

John, you're reporting a different issue than Bill - it would be best to keep these separate so to keep me from getting confused. I will move your issue to a separate thread.

[Steven_L_Intel1]

Hmm - well, I took your project, didn't touch anything and just clicked Start. It stopped at the breakpoint. Really all I can suggest at the moment is to uninstall Parallel Studio XE (Fortran) and reinstall, then see how it behaves.

[mecej4]

My comment in #3 should have stayed back in Billsincl's thread, because it is in response to https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/607690#comment-1858700 .

[JohnNichols]

I thought that would be the suggestion - I will try it tonight.

[Steven_L_Intel1]

mecej4, it applies here too. As does my comment. I will repost mine and you can repost yours. (I can't copy posts.)

[WSinc]

I normally do a "rebuild" which forces everything to be compiled at once.

so, the "out of date" thing would not apply there, correct ?

[Steven_L_Intel1]

Correct

[JohnNichols]

Steve:

I deleted VS 2013 and IF - I reinstalled VS 2012 and IF from scratch - created a new console application and still get the error - these are messages on build - any ideas

John

'Console1.exe' (Win32): Loaded 'C:\Users\macne\Documents\Visual Studio 2012\Projects\Console1\Console1\Debug\Console1.exe'. Symbols loaded.
'Console1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file.
'Console1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file.
'Console1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file.
'Console1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcr110d.dll'. Symbols loaded.
'Console1.exe' (Win32): Loaded 'C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.1.146\windows\redist\ia32_win\compiler\libifcoremdd.dll'. Module was built without symbols.
'Console1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imagehlp.dll'. Cannot find or open the PDB file.
'Console1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Cannot find or open the PDB file.

[Steven_L_Intel1]

The messages when you start to debug (not build) don't say anything important, other than the first one indicating that your program does have debugging symbols. The others you can ignore since you are not trying to debug those DLLs.

Where are you trying to set the breakpoint? The research I've done on this error all points to needing to do a debug build of the application, but I am sure you are doing that. I wonder if there's some other software on your system (such as an antivirus program) that is interfering with your debugging.

[JohnNichols]

Steve:

I am running the latest Windows 10 Insider Build 14251.

It is so stock standard it is not funny.  I use the built in Virus protection and most of my programs are Microsoft Office etc. AutoCAD etc..

It started on this machine straight after the update.  It also did exactly the same thing for the same programs on the home machine after the update. 

I have checked everything seems ok on the debug settings - 

This is a Dell Precision and the Home machine is ASUS P6T - funny it happened on both at the same time.

Have your developers tried the latest build

of course there is a price for sitting on the bleeding edge - it bleeds sometimes

John

[Steven_L_Intel1]

I am running Windows Insider builds at home. I will try some experiments there.

[JohnNichols]

Steve:

It appears to have been corrected with an update to the next VERSION of Windows on the P6T, I am still playing with the Dell

Thanks

John

[JohnNichols]

Steve:

The problem has gone away on both machines with the update - thanks for the support.

Interesting problem.

John

[Steven_L_Intel1]

Thanks for the update.