'cannot find or open the pdb file' Visual Studio C++ 2013
Visual StudioVisual Studio-2013C++builderVisual Studio Problem Overview
I just downloaded VS 2013 Community Edition and I wrote my first app. When I run it it shows in the output section:
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Users\Toshiba\Documents\Visual Studio 2013\Projects\ConsoleApplication1\Debug\ConsoleApplication1.exe'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\System32\msvcp120d.dll'. Cannot find or open the PDB file.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\System32\msvcr120d.dll'. Cannot find or open the PDB file.
The program '[11196] ConsoleApplication1.exe' has exited with code 0 (0x0).
What is the problem? I checked my code on many sites so I know that the problem is not in my code. Can anyone help me?
Visual Studio Solutions
Solution 1 - Visual Studio
Try go to Tools->Options->Debugging->Symbols and select checkbox "Microsoft Symbol Servers", Visual Studio will download PDBs automatically.
> PDB is a debug information file used by Visual Studio. These are > system DLLs, which you don't have debug symbols for.[...]
Solution 2 - Visual Studio
No problem. You're running your code under the debugger, and the debugger is telling you that it doesn't have debugging information for the system libraries.
If you really need that (usually for stack traces), you can download it from Microsoft's symbol servers, but for now you don't need to worry.
Solution 3 - Visual Studio
Working with VS 2013. Try the following
> Tools -> Options -> Debugging -> Output Window -> Module Load > Messages -> Off
It will disable the display of modules loaded.
Solution 4 - Visual Studio
It worked for me. Go to Tools-> Options -> Debugger -> Native and check the Load DLL exports. Hope this helps
Solution 5 - Visual Studio
There are no problems here this is perfectly normal - it shows informational messages about what debug-info was loaded (and which wasn't) and also that your program executed and exited normally - a zero return code means success.
If you don't see anything on the screen thry running your program with CTRL-F5 instead of just F5.
Solution 6 - Visual Studio
A bit late but I thought I'd share in case it helps anyone: what is most likely the problem is simply that your Debug Console (the command line window that opens when run your project if it is a Windows Console Application) is still open from the last time you ran the code. Just close that window, then rebuild and run: Ctrl + B and F5, respectively.