1) Without symbols
a) The faulting Stack
The stack backtrace of the thread that AV'd would look like:
b) The regiters values
c) The disassmbly code
2) With symbols including public symbols of "badExt.dll"
First, we need to add the symbol path(company wide symbols) as well as symbols of our dll
0:001> .sympath+ \\symbols\symbols
Symbol search path is: \\symbols\symbols
0:001> .sympath+ c:\symbols\public (where public symbols of badExt.dll are located)
Symbol search path is: \\symbols\symbols;c:\symbols\public
The stack backtrace of the thread that AV'd would look like:
Advanced Technique
To verify that the symbols are lined up properly for our extension, issue this command.
0:019>lmv mbadext
start end module name 06470000 06475000
badext M (pdb symbols) c:\symbols\public\badext.pdb
Loaded symbol image file: C:\Inetpub\wwwroot\Dev\badext.dll Image path: C:\Inetpub\wwwroot\Dev\badext.dll
Timestamp: Wed Jan 29 18:07:14 2003 (3E385EA2)
Checksum: 0000EBCD
File version: 5.0.0.0
Product version: 5.0.0.0
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
CompanyName: Microsoft Corporation
ProductName: Internet Information Services
InternalName: badEXT.dll
OriginalFilename: badEXT.dll
ProductVersion: 5.00.0984
FileVersion: 5.00.0984
FileDescription: badEXT Test
LegalCopyright: Copyright (C) Microsoft Corp. 1981-1999
3) with Private Symbols "badExt.dll"
The stack backtrace of the thread that AV'd would look like: