"No Symbolic Information" May Be Caused by Wrong Linker (59540)
The information in this article applies to:
- Microsoft CodeView for MS-DOS 2.2
- Microsoft CodeView for MS-DOS 3.0
- Microsoft CodeView for MS-DOS 3.11
- Microsoft CodeView for MS-DOS 3.14
- Microsoft CodeView for MS-DOS 4.0
- Microsoft CodeView for MS-DOS 4.01
- Microsoft CodeView for MS-DOS 4.05
- Microsoft CodeView for MS-DOS 4.1
- Microsoft CodeView for OS/2 2.2
- Microsoft CodeView for OS/2 3.0
- Microsoft CodeView for OS/2 3.11
- Microsoft CodeView for OS/2 3.12
- Microsoft CodeView for OS/2 3.5
- Microsoft CodeView for Windows 3.0
- Microsoft CodeView for Windows 3.05
- Microsoft CodeView for Windows 3.06
- Microsoft CodeView for Windows 3.07
- Microsoft CodeView for Windows 4.0
- Microsoft CodeView for Windows 4.01
- Microsoft CodeView for Windows 4.1
This article was previously published under Q59540 SYMPTOMS
CodeView generates the message "No Symbolic Information" and displays the
program in assembly language mode even though the source files were
compiled and linked with the correct options to specify CodeView symbolic
debugging information.
CAUSE
Different versions of the linker use different methods to store
symbolic information. A later version of CodeView generally can
display symbolic information for an application developed with earlier
versions of LINK, but the converse is not true. Problems can arise
when you use a recent version of LINK with an earlier version of
CodeView.
RESOLUTION
To debug an application at the source code level with CodeView, you
must use the correct version of Microsoft LINK. Each CodeView version
has a corresponding LINK version. If you use a version of LINK
released after the version designed for your version of CodeView,
CodeView might not recognize the symbolic information in the .EXE
file.
Modification Type: | Major | Last Reviewed: | 12/1/2003 |
---|
Keywords: | kb16bitonly KB59540 |
---|
|