Solved

Visual C++ 5.0

Posted on 1997-05-05
8
189 Views
Last Modified: 2010-04-10
After installing Version 5 of  Visual C++ I get the following error message when I load an app from the debugger.

 no matching symbolic information found.

What can I do to get rid of these messages?
0
Comment
Question by:gemme
8 Comments
 
LVL 4

Expert Comment

by:md041797
Comment Utility
Set your compiler and linker to generate debugingging information.
0
 

Author Comment

by:gemme
Comment Utility
These appear after notification that a DLL is loaded.  These are microsoft DLL's, not mine.
0
 

Author Comment

by:gemme
Comment Utility
These appear after notification that a DLL is loaded.  These are microsoft DLL's, not mine.
0
 
LVL 1

Expert Comment

by:jungel
Comment Utility
It would help if you reproduced the complete error message.  There IS more to it.
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 

Expert Comment

by:Ng050597
Comment Utility
Have you tried deleting all OBJ and EXE files and recompiling from scratch.  There might be a version problem.
0
 

Author Comment

by:gemme
Comment Utility
here is a little more of the error messages.  I get about 20-30 of these.
I am running NT version 4.0 service pack 2

Loaded 'D:\WINNT\system32\KERNEL32.DLL', no matching symbolic information found.
Loaded 'D:\WINNT\system32\gdi32.dll', no matching symbolic information found.
Loaded 'D:\WINNT\system32\USER32.DLL', no matching symbolic information found.
Loaded 'D:\WINNT\system32\ADVAPI32.DLL', no matching symbolic information found.
Loaded 'D:\WINNT\system32\RPCRT4.DLL', no matching symbolic information found.
Loaded 'D:\WINNT\system32\ODBC32.DLL', no matching symbolic information found.
Loaded 'D:\WINNT\system32\msvcrt40.dll', no matching symbolic information found.
0
 
LVL 3

Accepted Solution

by:
LucHoltkamp earned 50 total points
Comment Utility
These DLL's (and apps) don't contain symbolic information (such as identifier names, line numbers etc..). When you load an app with the debugger it assumes you want to debug it, a task where the presence of symbolic information is very usefull. Basically you would only load apps with the debugger that you wrote yourself, and that need debugging. For these you can set the compiler and linker to generate debug info, as md noted.

0
 

Author Comment

by:gemme
Comment Utility
Thank you!
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Suggested Solutions

Often, when implementing a feature, you won't know how certain events should be handled at the point where they occur and you'd rather defer to the user of your function or class. For example, a XML parser will extract a tag from the source code, wh…
Introduction This article is a continuation of the C/C++ Visual Studio Express debugger series. Part 1 provided a quick start guide in using the debugger. Part 2 focused on additional topics in breakpoints. As your assignments become a little more …
The viewer will learn how to use the return statement in functions in C++. The video will also teach the user how to pass data to a function and have the function return data back for further processing.
The viewer will learn additional member functions of the vector class. Specifically, the capacity and swap member functions will be introduced.

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now