Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 259332 - Last Review: February 12, 2007 - Revision: 1.2
How To Windows 98 DDK: Building Symbol Files with Line Number Information
This article was previously published under Q259332
By default, the Windows 98 DDK Checked Build Environment does not build symbol files that contain line number information. To use WDEB98/RTERM98 source-level debugging, the symbol file must contain line number information.
To build symbol files that contain line-number information, modify the following files:
- Modify the Makefile.def file in the Win98\Inc
folder to cause the linker to use the correct linker options
to build a .map file with line-number information.
- Use the Mapsym.exe file, once the correct link options are used, to build a .sym file with line-number information that matches your .sys file. Follow these steps:
- In your SOURCES file for the driver you are building, add the following line:
- Edit the DDK\Inc\Makefile.def file and make the following changes:
Change the line that reads as follows (should be line 1138)
LINKER_DBG_SECTION=-debug:notmapped,FULL
LINKER_DBG_SECTION=-debug:FULL
LINKER_DBG_TYPE = -debugtype:both
LINKER_DBG_TYPE = -debugtype:MAP,COFF
- Rebuild the driver. You should see a (driver_Name).map file
in the Win98ddk\Lib\i386\Checked folder. You can check for line-number information by opening the .map file and checking to see if it contains line numbers near the bottom of the file.
- With line-number information, you can specify a code search path in RTERM98. You should then see the source window open when a breakpoint is hit in the driver.
See the Windows 98 DDK for more information on building and debugging drivers.
APPLIES TO
- Microsoft Windows 98 Driver Development Kit (DDK)
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate