Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Crpytic error messages

WSinc
New Contributor I
402 Views

Iget these every time I enter "stop debugging" in the VS.
This is just a nuisance, but I am wondering if there's something I'm doing wrong, that
can be easily corrected.
These DLLs are not something I use directly.
Any ideas?
*******************************************************************************

'CHESS.exe': Loaded 'D:\\William Data\\My Documents\\Visual Studio 2010\\Projects\\CHESS\\CHESS\\CHESS\\Debug\\CHESS.exe', Symbols loaded.

'CHESS.exe': Loaded 'C:\\Windows\\System32\\ntdll.dll', Cannot find or open the PDB file

'CHESS.exe': Loaded 'C:\\Windows\\System32\\kernel32.dll', Cannot find or open the PDB file

'CHESS.exe': Loaded 'C:\\Windows\\System32\\KernelBase.dll', Cannot find or open the PDB file

'CHESS.exe': Loaded 'C:\\Program Files\\AVAST Software\\Avast\\snxhk.dll', Cannot find or open the PDB file

'CHESS.exe': Loaded 'C:\\Windows\\System32\\imagehlp.dll', Cannot find or open the PDB file

'CHESS.exe': Loaded 'C:\\Windows\\System32\\msvcrt.dll', Cannot find or open the PDB file

'CHESS.exe': Loaded 'C:\\Program Files\\Intel\\Composer XE 2011 SP1\\redist\\ia32\\compiler\\1033\\ifcore_msg.dll', Binary was not built with debug information.

'CHESS.exe': Loaded 'C:\\Program Files\\Intel\\Composer XE 2011 SP1\\redist\\ia32\\compiler\\1033\\irc_msg.dll', Binary was not built with debug information.

'CHESS.exe': Loaded 'C:\\Windows\\System32\\dbghelp.dll', Cannot find or open the PDB file

CHESS.exe has triggered a breakpoint

The program '[3972] CHESS.exe: Native' has exited with code -1073741510 (0xc000013a).

0 Kudos
1 Reply
Steven_L_Intel1
Employee
402 Views
These are not error messages - they are all informational.

The "Loaded" messages are progress messages from the debugger listing for the EXE and each DLL whether or not debug symbols have been loaded. By default, you won't get symbols for run-time DLLs.

The breakpoint message should be self-explanatory - it is issued when the program breaks in the debugger for some reason.

The last message tells you that the program exited with an exit status. For a successful exit, this is usually 0.
0 Kudos
Reply