no matching symbolic information found.

  • Thread starter Thread starter solarin
  • Start date Start date
S

solarin

Hi,

I've developed a program under VS 6.0. I can compile it and run it, but
when I try to debbug , all my breakpoints are dissabled and I can see
the following messages:

Loaded 'D:\prj\simulador HMS\Enviar Datos al sim\CMS\Debug\CMS.exe', no
matching symbolic information found.
Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\kernel32.dll', no matching symbolic
information found.
Loaded symbols for 'C:\WINDOWS\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MSVCRTD.DLL'
Loaded 'C:\WINDOWS\system32\gdi32.dll', no matching symbolic
information found.
Loaded 'C:\WINDOWS\system32\user32.dll', no matching symbolic
information found.
Loaded symbols for 'C:\WINDOWS\system32\MFCO42D.DLL'
Loaded 'C:\WINDOWS\system32\mfc42loc.dll', no matching symbolic
information found.

How can I fix this?

Thanks for your support.
 
I've developed a program under VS 6.0. I can compile it and run it, but
when I try to debbug , all my breakpoints are dissabled and I can see
the following messages:
Loaded 'D:\prj\simulador HMS\Enviar Datos al sim\CMS\Debug\CMS.exe', no
Click to expand...

This seems to indicate that you are running a debug build, but VC cannot
find symbolic information. did you change your debug settings?
Does this also happen in other projects?
matching symbolic information found.
Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\kernel32.dll', no matching symbolic
information found.
Loaded symbols for 'C:\WINDOWS\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MSVCRTD.DLL'
Loaded 'C:\WINDOWS\system32\gdi32.dll', no matching symbolic
information found.
Loaded 'C:\WINDOWS\system32\user32.dll', no matching symbolic
information found.
Loaded symbols for 'C:\WINDOWS\system32\MFCO42D.DLL'
Loaded 'C:\WINDOWS\system32\mfc42loc.dll', no matching symbolic
information found.
Click to expand...

You get these warnings because you didn't install the OS symbols.
This is harmless unless you want to track down a problem inside the system
APIs, or if you want to follow the stack trace into the system.
Normally it should find the MFC debug information I think, but perhaps you
did not install MFC completely?
 
Back
Top