FIX: TRACE Error TR1013, TR4001, and TR4002 Causes |
Q92402
The information in this article applies to:
- Microsoft Trace Utility for MS-DOS, versions 1.0, 1.1
SYMPTOMS
In the Microsoft Trace Utility (TRACE), using the /EXE option can cause the following error message in TRACE version 1.0:
TR1013: invalid debugging information
When the error occurs, TRACE does not generate any output. In TRACE version 1.1, the following warning messages may appear:
TR4001: cannot find function name
TR4002: missing debugging information for module
In the trace output, functions are identified by overlay number and offset rather than by function name.
RESOLUTION
This situation usually occurs when the application declares overlays using the SEGMENT statement in the module definition (DEF) file. In some cases, you can avoid this problem in one of two ways:
- Specify the overlays on the LINK command line using the old overlay syntax (using parentheses to group object modules into overlays)
- Compile the application with function packing (specified by the /Gy compiler switch) and use the FUNCTIONS statement in the DEF file.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft Trace Utility versions 1.0 and 1.1 for MS-DOS. This problem was corrected in Microsoft Trace Utility version 1.2 for MS-DOS.
MORE INFORMATION
The MOVEAPI.TXT file, provided with Microsoft C/C++ version 7.0, describes the /EXE option for the TRACE utility as follows:
/EXE:filename
Allows TRACE to read the executable file that was traced and extract function names for use in the trace output. Specify the filename of the executable file that generated the MOVE.TRC file. You can specify a path with the filename. If /EXE is not specified, the trace output refers to functions by overlay number and offset.
The program must contain Microsoft Symbolic Debugging Information that is compatible with Microsoft CodeView version 4.0. To include debugging information, create the object file using the /Zi option and link the program using the /CO option.
However, as indicated above, this syntax does not work properly in TRACE versions 1.0 and 1.1.
Additional query words: 1.00 1.10 1.20 7.00 ENDUSER | buglist1.00 buglist1.10 fixlist1.20
Keywords : kb16bitonly
Issue type :
Technology : kbAudDeveloper kbTrace kbTrace100 kbTrace110 kbREVIEWSearch
Last Reviewed: October 30, 1999 |
