与Visual Studio 2010中的.dll相关的错误

Question

I am new to visual studio.I keep encountering the below error when I go to debug mode in VS.

'something.exe': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Cannot find or open the PDB file
'something.exe': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Cannot find or open the PDB file
'something.exe': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Cannot find or open the PDB file
'something.exe': Loaded 'C:\Windows\SysWOW64\msvcr100d.dll', Symbols loaded.
The program '[792] something.exe: Native' has exited with code 0 (0x0).

I have tried Tools->Options->Debugging->Symbols and checking Microsoft Symbols Server but again the problem persists as shown below

 'something.exe': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Symbols loaded (source information stripped).
    'something.exe': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Symbols loaded (source information stripped).
    'something.exe': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Symbols loaded (source information stripped).
    'something.exe': Loaded 'C:\Windows\SysWOW64\msvcr100d.dll', Symbols loaded (source information stripped).
    The program '[8592] something.exe: Native' has exited with code 0 (0x0)

Any help will much be appreciated. Regards, newbie_in

Answer 1

The first four lines (in both cases) have nothing to do with your program. In the first case they are saying that the debugger doesn't know anything about functions in each of the DLLs, in the second case they are saying it does. (That can be particularly helpful when there are callbacks from DLLs to your code).

In both cases your program is running and exiting normally.

(The bit about "source information stripped" just means that Microsoft don't let debugging information with line numbers and filenames outside Microsoft. It's harmless too.)

You probably need to put a breakpoint in your code if you want to debug it.

Answer 2

A PDB file is a program database which contains debug symbols for already compiled code. ntdll.dll , kernel32.dll and KernelBase.dll are Windows kernel DLLs, msvcr100d.dll is the Microsoft Visual 2010 (v10.0) C runtime.

Your first code block tells us, that these DLLs have no PDB file, so cannot properly be analyzed for debugging (which you should never need, so it's no problem). It's just a warning, no error, everything runs ok to the end with exit code 0.

The second code block found these symbols, so if you should ever send your data into kernel functions, like a callback, you can find your faults.