When starting a program under the Microsoft Visual Studio* debugger, you will generally see in the Output pane a series of messages similar to the following:
'Project01.exe' (Win32): Loaded '<C:\Users\yourname\Documents\Visual Studio 2013\Projects\Project01\Debug\Project01.exe>'. Symbols loaded.'Project01.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file.'Project01.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file.'Project01.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file.'Project01.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcp120d.dll'. Cannot find or open the PDB file.'Project01.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcr120d.dll'. Cannot find or open the PDB file.
These are not error messages - they are informational messages from the Visual Studio debugger listing the various executables and Dynamic Link Libraries (DLLs) that have been loaded, and whether or not the PDB (Program DataBase) file containing debug symbol information was found. Normally, the PDB file for your application will be found, as it was here, but PDBs for run-time and system DLLs will not. Unless you plan to debug the system DLLs you don't need their PDB files and should ignore these messages.
You may also see a message similar to:
The program '[11536] Project01.exe' has exited with code 0 (0x0).
This indicates that the program ran to completion and exited - here with a success status of zero. If you see this message immediately following the "Loaded" messages above, without having the program break into the debugger, you will want to set a breakpoint at the first executable line in the program and then run it again. For C++ applications this is usually not necessary, but it is required for Fortran applications.
If you need further assistance, please ask in our User Forums or use Intel® Premier Support.