VB5SP3DS.EXE Contains Visual Basic SP3 Debugging Symbols (188588)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q188588 SUMMARY Microsoft has made available to the public debugging
symbols to aid in the debugging of applications created with Microsoft Visual
Basic 5.0 Service Pack Three (SP3) components. These symbols allow debugging
tools such as Visual C++, Dr. Watson, NTSD/CDB, and WinDBG to obtain stack
traces describing the functions within built components, such as MSVBVM50.DLL,
that are being called when a crash occurs. These traces would aid developers
and Microsoft support engineers in diagnosing the problems. MORE INFORMATIONThe
following file is available for download from the Microsoft Download
Center: For
additional information about how to download Microsoft Support files, click the
following article number to view the article in the Microsoft Knowledge Base: 119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most
current virus-detection software that was available on the date that the file
was posted. The file is stored on security-enhanced servers that help to
prevent any unauthorized changes to the file.
To install the debugging symbols, first
extract them from VB5SP3DS.EXE. When VB5SP3DS.EXE is run, it will prompt you
for a directory (default: C:\WINNT) in which to extract the files. At
completion, the following directory tree will be created below the directory
you have chosen:
\SYMBOLS\dll
07/19/97 04:54p 1,340 vb5en.dbg
07/19/97 04:59p 136,616 MSConDes.dbg
07/19/97 04:59p 583,236 MSRDO20.dbg
07/19/97 04:54p 2,679,216 MSVBVM50.dbg
07/19/97 04:45p 168,292 VB5DB.dbg
07/19/97 04:59p 38,696 MSCDRun.dbg
07/19/97 04:45p 1,672 vb5ide.dbg
10/01/97 11:48a 2,769,076 VBA5.dbg
\SYMBOLS\exe
07/19/97 04:45p 3,453,180 VB5.dbg
\SYMBOLS\ocx
07/19/97 04:59p 224,428 comct232.dbg
09/17/97 09:07p 298,884 DBList32.dbg
07/19/97 04:59p 146,792 ComDlg32.dbg
07/19/97 04:59p 713,896 ComCtl32.dbg
07/19/97 04:59p 216,072 mci32.dbg
07/19/97 04:59p 140,332 MSComm32.dbg
07/19/97 04:59p 281,260 msflxgrd.dbg
09/11/97 09:24p 161,384 msinet.dbg
07/19/97 04:59p 176,916 msmapi32.dbg
07/19/97 04:59p 170,632 MSMask32.dbg
07/19/97 05:00p 143,064 mswinsck.dbg
07/19/97 05:00p 129,684 PicClp32.dbg
07/19/97 05:00p 256,740 RichTx32.dbg
07/19/97 05:00p 95,932 SysInfo.dbg
07/19/97 05:00p 298,772 tabctl32.dbg
07/19/97 04:59p 183,320 MSRDC20.dbg
These .dbg files are for debugging Visual Studio SP3 components
on Intel platforms only. Different debugging tools have different
methods of locating debugging symbols. Usually, you can put a .dbg file in the
same directory as the corresponding .exe, .dll, or .ocx file. For instance,
MSVBVM50.DLL is in C:\Winnt\System32 directory; you can copy Msvbvm50.dbg to
C:\Winnt\System32 and most debuggers will find it. Some debuggers are set up by
default to find symbols in the Symbols directory if it exists below your system
root directory (for example C:\WINNT\Symbols\). You should consult your
debugger documentation for more information before installing the symbols.
The .dbg files in VB5SP3DS.EXE contain symbols in the Common Object
File Format (COFF). To use them with Visual C++ 5.0, you may need to copy
SYMCVT.DLL from your Visual C++ CD-ROM to your Windows system (system32 for NT)
directory. DRWTSN32.EXE shipped with NT understands COFF symbols without
SYMCVT.DLL.
| Modification Type: | Minor | Last Reviewed: | 7/26/2005 |
|---|
| Keywords: | kbdownload kbBug kbDebug kbfile kbinfo KB188588 |
|---|
|