Wer kennt sich mit dem Micorsoft Debugger aus?

[eras 10]

Hey all,

 

Ich benutze öfter mal den MS Debugger um die kleinen Crashdumps zu öffnen. Das ist of sehr hilfreich da einem dieser oft zeigt welche Datei den Fehlerverursacht haben könnte. Aber eines Quält mich schon seit Anfang an: Die Symbols!

 

Kann mit bitte jemand Erklären was diese Symbols sein sollen?

 

Ich bekomme nämlich bei der auswertung ständig die Meldung das die Symbols nicht geladen werden konnten und das ich das fixen soll. Mein Symbol path ist SRV*D:\symbols*http://msdl.microsoft.com/download/symbols aber das haut irgendwie nicht hin :(

 

Hier mal ein Auszug einer solchen Auswertung:

[eras 10]

Wegen der zeichenbeschränkung, zwei Posts...

 

Microsoft ® Windows Debugger Version 6.5.0003.7

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [X:\TS\MEMORY.DMP]

Kernel Complete Dump File: Full address space is available

 

************************************************************

WARNING: Dump file has been truncated. Data may be missing.

************************************************************

Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -

Windows Server 2003 Kernel Version 3790 (Service Pack 1) UP Free x86 compatible

Product: Server, suite: TerminalServer

Built by: 3790.srv03_sp1_rtm.050324-1447

Kernel base = 0x80800000 PsLoadedModuleList = 0x808a8e48

Debug session time: Tue Nov 29 09:29:17.086 2005 (GMT+1)

System Uptime: 0 days 2:02:00.250

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -

Loading Kernel Symbols

.....................................................................................................................

Loading unloaded module list

..........

Loading User Symbols

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck A, {817f27f7, 2, 0, 808324ed}

 

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

 

*** WARNING: Unable to verify timestamp for mssmbios.sys

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

 

Followup: MachineOwner

---------

[cablit 10]

Hi eras,

 

About the Microsoft Symbol Server

 

Symbol server technology is built into Debugging Tools for Windows. Microsoft provides access to an Internet symbol server that contains symbol files for the Microsoft Windows Server 2003, Windows XP, and Windows 2000 operating systems, as well as other Microsoft products.

 

The Internet symbol server is populated with a variety of Windows symbols for Microsoft Windows operating systems, including hot fixes, Service Packs, Security Rollup Packages, and retail releases. Symbols are also available on the server for current Betas and Release Candidates for Windows products, plus a variety of other Microsoft products, such as Microsoft Internet Explorer.

 

If you have access to the Internet during debugging, you can configure the debugger to download symbols as needed during a debugging session, rather than downloading symbol files separately before a debugging session. The symbols are downloaded to a directory location that you specify and then the debugger loads them from there.

 

To use the Microsoft Symbol Server

 

1. Make sure you have installed the latest version of Debugging Tools for Windows.

 

2. Start a debugging session.

 

3. Decide where to store the downloaded symbols (the "downstream store"). This can be a local drive or a UNC path.

 

4. Set the debugger symbol path as follows, substituting your downstream store path for DownstreamStore.

 

SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols

 

For example, to download symbols to c:\websymbols, you would add the following to your symbol path:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

 

Note: http://msdl.microsoft.com/download/symbols is not browsable and is intended only for access by the debugger. For more information on setting symbol paths and using symbol servers, see the documentation accompanying Debugging Tools for Windows.

 

aus Debugging Tools and Symbols

 

Hilft dir das schon weiter?

 

Grüße

[eras 10]

Ja ein bisschen schon danke. Aber ich weiß noch immer nicht was diese "Symbols" überhaupt sind?

[cablit 10]

Hi,

 

bei Download Windows Symbol Packages findest du zu deinem BS und deinem Prozessor passende Symbol-Pakete. Dieses Paket bei dir installiert, erzeugt ein Symbols-Verzeichnis mit PDB- und DBG-Dateien.

 

"If you have symbol information, you’d be able to see function names and their arguments in your call stack. If the binaries and PDBs are from your application, you’d additionally have information about private functions, local variables and type information." (aus Windows Debuggers: Part 1: A WinDbg Tutorial

 

Grüße