DOCUMENT:Q176547  12-NOV-1997  [vbwin]
TITLE   :FILE: VB5SP2DS.EXE: Visual Basic SP2 Debugging Symbols
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0; WINNT:97sp2
OPER/SYS:WINDOWS winnt
KEYWORDS:vb5all

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 5.0
 - Microsoft Visual Studio, version 97 sp2
---------------------------------------------------------------------

SUMMARY
=======

Microsoft has made available to the public debugging symbols to aid in the
identification of bugs within Microsoft Visual Basic 5.0 with Visual Studio
SP2 applied. Debugging symbols allow debugging tools like Visual C++ and
Dr. Watson to obtain stack traces describing the functions within built
components, such as MSVBVM50.DLL, which are being called when a crash
occurs. These traces aid Microsoft in diagnosing problems that cannot be
easily reproduced on other systems.

MORE INFORMATION
================

The following file is available for download from the Microsoft
Software Library:

 ~ Vb5sp2ds.exe

For more information about downloading files from the Microsoft Software
Library, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services

To install the debugging symbols, you first must extract them from
VB5SP2DS.EXE. When you run the VB5SP2DS.EXE, it will prompt you for a
directory in which to extract the files. When the extraction process is
complete, there will be two sub-directories containing the debugging symbol
files. These files all have a DBG file extension.

The DBG files in the "x86" directory are for debugging Visual Studio
Service Pack 2 on Intel platforms. The DBG files in the "Alpha" directory
are for debugging Visual Studio Service Pack 2 on the Alpha platform.

Different debugging tools have different methods of locating debugging
symbols. Usually, you can put a DBG file in the same directory as the EXE,
DLL, or OCX for which it applies and a debugging tool will find it. For
instance, if MSVBVM50.DLL is in C:\WINNT\SYSTEM32 directory, you can copy
MSVBVM50.DBG to C:\WINNT\SYSTEM32 and most debugging tools will locate it.
You should consult your debugging tool documentation for more information
on installing debugging symbols so that the tool can use them.

Additional query words: Debugging, SP2, DBG
======================================================================
Keywords          : vb5all
Version           : WINDOWS:5.0; WINNT:97sp2
Platform          : WINDOWS winnt
Issue type        : kbinfo
Solution Type     : kbfile

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1997.