Debug Labs


Unhandled Exception in Component Code (Software  CONTINUABLE)

This lab will demonstrate an Unhandled Exception in a component. In this scenario, an Unhandled Exception in the ISAPI filter "badFil.dll".

This scenario is presented in 2 variations, the 1st variation shows the unhandled exception in the main thread running the HTTPFilterProc, while the second variation shows the unhandled exception in a spawned thread other than the main thread.

In both variations, the Unhandled Exception is caused by a CONTINUABLE exception implemented by a call to RaiseException(...).

1- Lab Setup
	

Note: This lab assumes that you have already installed the necessary lab files to run it.

1-Install the ISAPI Filter

 

- Right Click the Server Name

- Click "Properties"

- In the "WWW Service" Master Properties, click "Edit"

- In the "ISAPI Filters" tab, click "Add"

- In the "Filter Name" type in "BadFilter"

- In the "Executable", browse to C:\IISDebugLabs\www\App\badfil.dll

- Click "Apply" and click "Ok" all teh way out.

 

2- Restart the IIS Admin service

- Right Click the Server Name

- Click "Restart IIS" and Click "Ok"

 

3- Attach the debugger to inetinfo.exe

a) Using the GUI:

- Click "File"

- Click "Attach to Process"

- Select "inetinfo.exe" and click "OK"

b) Using the command prompt

-Type in "windng -pn inetinfo.exe" without quotation marks and hit "Enter"

 

4- In windbg command line, type in "g" with no quotation marks and press Enter

 

 

2- Run Scenario

1- Click the "Cause Unknown Exception V:1" button the first time to cause a 1st chance Unknown Exception in inetinfo.exe.
 Note that the debugger breaks and diplays 
	a- Comments about the exception
b- The value of the registers
c- The module where the Exception happened
d- The assembly line that caused the Exception
3- To study the second variation of this lab, click the "Cause Unknown Exception V:2" button.

                

1) Unhandled Exception in the main thread running HttpExtensionProc:  (Variation 1)

1- Debug Annotation

 

1) Without symbols

 

 

a) The faulting Stack

 

The stack backtrace of the thread that caused the Unhandled Exception would look like:

 

0:008> kvn50

# ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00 0129f5bc 016b1da2 00000057 00000000 00000000 KERNEL32!RaiseException+0x37

01 0129f5dc 016b17c0 00000001 00e84f20 00e84e00 badfil!HttpFilterProc+0x8a0

02 0129fbf4 65f0354f 00000001 00004000 08000002 badfil!HttpFilterProc+0x2be

03 0129fc1c 65f034bc 000003e8 00004000 00000002 w3svc!STR::Copy+0x11a

04 0129fc50 65f02cad 0129fedc 0129fedc 00e84648 w3svc!STR::Copy+0x87

05 0129fca8 65f02ac1 006a9030 0000019b 0129fcd4 w3svc!CLIENT_CONN::OnSessionStartup+0xa69

06 0129fcec 65f029b5 006a9030 0000019b 0129fedc w3svc!CLIENT_CONN::OnSessionStartup+0x87d

07 0129fd2c 65f028f8 0129fea4 0129fedc 0129feb8 w3svc!CLIENT_CONN::OnSessionStartup+0x771

08 0129fd4c 65f027b3 0129fea4 0129fedc 0129feb8 w3svc!CLIENT_CONN::OnSessionStartup+0x6b4

09 0129fec4 65f020d7 0129fedc 011a3568 0129ff20 w3svc!CLIENT_CONN::OnSessionStartup+0x56f

0a 0129fee4 65f01b47 00000000 00000000 00000000 w3svc!HTTP_HEADERS::Reset+0x311

0b 0129ff08 65f01aa5 0129ff20 77e873b2 011a3568 w3svc+0x1b47

0c 0129ff4c 6d701443 011a3568 0000019b 00103880 w3svc+0x1aa5

0d 0129ff80 6d702203 00000000 0000019b 011a356c ISATQ!AtqReadSocket+0x228

0e 77deec86 ece868ff fb6877dc 6477db19 000000a1 ISATQ!AtqWriteSocket+0x495

0f 6aec8b55 00000000 00000000 00000000 00000000 0xece868ff

 

This call stack shows that an exception of code (00000057) was raised in "badFil.dll". This exception is a software exception that translates to "ERROR_INVALID_PARAMETER". In this case,

the exception is CONTINUABLE (Second parameter of RaiseException is 0) which means that even if it not handled, execution could continue.

 

Again, In this call stack, it is clear that the culprit is "badFil.dll". So it is enough to tell the customer to contact the dll vendor to fix it. If it is an in-house component and the customer would like help

from Microsoft, they should open an advisory case to troubleshoot the issue further.

 

 

2) With symbols including public symbols of "badFil.dll"

 

 

First, we need to add the public symbol path(company wide symbols) as well as symbols of our dll

a) Using the GUI:

- Click "File"

- Click "Symbol File Path"

- Type in SRV*C:\LabSymbols*http://msdl.microsoft.com/download/symbols;C:\IISDebugLabs\symbols\Pub and hit Enter

b) Using the ".sympath+" command:

0:008> .sympath+ SRV*C:\LabSymbols*http://msdl.microsoft.com/download/symbols

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

 

0:008> .sympath+ C :\IISDebugLabs\symbols\Pub (where public symbols of badFil.dll are located)

Symbol search path is:SRV*C:\LabSymbols*http://msdl.microsoft.com/download/symbols; C :\IISDebugLabs\symbols\Pub

 

Note: For more information on setting the symbol path for windbg, please refer to the debugger documentation for the .sympath command. This will describe

the "downstream store" feature that lets you download symbols to a symbol server of your own.

 

 

The stack backtrace of the thread that caused the Unhandled Exception would look like:

 

0:008> kvn50

# ChildEBP RetAddr Args to Child

00 0129f5bc 016b1da2 00000057 00000000 00000000 KERNEL32!RaiseException+0x56 (FPO: [Non-Fpo])

01 0129f5dc 016b17c0 00000001 00e84f20 00e84e00 badfil!doRE1+0x18

02 0129fbf4 65f0354f 00000001 00004000 08000002 badfil!HttpFilterProc+0x2be

03 0129fc1c 65f034bc 000003e8 00004000 00000002 w3svc!FILTER_LIST::NotifyFilters+0x9d (FPO: [Non-Fpo])

04 0129fc50 65f02cad 0129fedc 0129fedc 00e84648 w3svc!HTTP_FILTER::NotifyPreProcHeaderFilters+0x3e (FPO: [Non-Fpo])

05 0129fca8 65f02ac1 006a9030 0000019b 0129fcd4 w3svc!HTTP_REQUEST::Parse+0x372 (FPO: [Non-Fpo])

06 0129fcec 65f029b5 006a9030 0000019b 0129fedc w3svc!HTTP_REQ_BASE::OnCompleteRequest+0x28 (FPO: [Non-Fpo])

07 0129fd2c 65f028f8 0129fea4 0129fedc 0129feb8 w3svc!HTTP_REQ_BASE::UnWrapRequest+0x1e6 (FPO: [Non-Fpo])

08 0129fd4c 65f027b3 0129fea4 0129fedc 0129feb8 w3svc!HTTP_REQ_BASE::OnFillClientReq+0x6c (FPO: [Non-Fpo])

09 0129fec4 65f020d7 0129fedc 011a3568 0129ff20 w3svc!HTTP_REQUEST::DoWork+0x8b (FPO: [Non-Fpo])

0a 0129fee4 65f01b47 00000000 00000000 00000000 w3svc!CLIENT_CONN::DoWork+0x1aa (FPO: [Non-Fpo])

0b 0129ff08 65f01aa5 0129ff20 77e873b2 011a3568 w3svc!CreateClient+0x7b (FPO: [Non-Fpo])

0c 0129ff4c 6d701443 011a3568 0000019b 00103880 w3svc!W3OnConnectEx+0x118 (FPO: [Non-Fpo])

0d 0129ff80 6d702203 00000000 0000019b 011a356c ISATQ!AtqpProcessContext+0x23a (FPO: [Non-Fpo])

0e 0129ffb4 77e887dd abcdef01 00000000 00012047 ISATQ!AtqPoolThread+0x1a8 (FPO: [EBP 0x0129ffec] [1,4,4])

0f 0129ffec 00000000 6d7091f7 abcdef01 00000000 KERNEL32!BaseThreadStart+0x52 (FPO: [Non-Fpo])

 

 

So, this shows that the RaiseException call in kernel32 came from the function (doRE1) in "badFil.dll".

 

Again, In this stack backtrace, it is clear that the culprit is "badFil.dll". So it is enough to tell the customer to contact the dll vendor to fix it. If it is an in-house component and the customer would like help

from Microsoft, they should open an advisory case to troubleshoot the issue further.

 

3) with Private Symbols "badExt.dll"

 

 

Point the debugger to use the private symbols

For company wide internal symbols, use \\symbols\symbols

For the component private symbols, use C:\IISDebugLabs\Symbols\Pri

 

Verify the component symbols are linet up.

 

0:008> lmv mbadfil

start end module name

015a0000 015a6000 badfil (pdb symbols) C:\IISDebugLabs\Symbols\Pri

Loaded symbol image file: badfil.dll

Image path: C:\IISDebugLabs\www\App\badfil.dll

Timestamp: Wed May 28 01:11:01 2003 (3ED444E5)

Checksum: 0000D9A0

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: badFIL.dll

OriginalFilename: badFIL.dll

ProductVersion: 5.00.0984

FileVersion: 5.00.0984

FileDescription: badFIL Filter DLL

LegalCopyright: Copyright (C) Microsoft Corp. 1981-1999

 

 

 

The stack backtrace of the thread that caused the Unhandled Exception would look like:

 

0:008> kvn50

# ChildEBP RetAddr Args to Child

00 0129f5bc 016b1da2 00000057 00000000 00000000 KERNEL32!RaiseException+0x56 (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\windows\base\client\thread.c @ 1382]

01 0129f5dc 016b17c0 00000001 00e84f20 00e84e00 badfil!doRE1+0x18 (CONV: stdcall) [H:\nT\PRIVATE\inet\iis\svcs\w3\gateways\filDBG\badfil.cpp @ 776]

02 0129fbf4 65f0354f 00000001 00004000 08000002 badfil!HttpFilterProc+0x2be (CONV: stdcall) [H:\nT\PRIVATE\inet\iis\svcs\w3\gateways\filDBG\badfil.cpp @ 297]

03 0129fc1c 65f034bc 000003e8 00004000 00000002 w3svc!FILTER_LIST::NotifyFilters+0x9d (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\httpfilt.cxx @ 968]

04 0129fc50 65f02cad 0129fedc 0129fedc 00e84648 w3svc!HTTP_FILTER::NotifyPreProcHeaderFilters+0x4c (FPO: [Non-Fpo]) (CONV: thiscall) [.\filter.hxx @ 473]

05 0129fca8 65f02ac1 006a9030 0000019b 0129fcd4 w3svc!HTTP_REQUEST::Parse+0x380 (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\httpreq.cxx @ 1497]

06 0129fcec 65f029b5 006a9030 0000019b 0129fedc w3svc!HTTP_REQ_BASE::OnCompleteRequest+0x36 (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\httpio.cxx @ 1289]

07 0129fd2c 65f028f8 0129fea4 0129fedc 0129feb8 w3svc!HTTP_REQ_BASE::UnWrapRequest+0x1f4 (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\httpio.cxx @ 634]

08 0129fd4c 65f027b3 0129fea4 0129fedc 0129feb8 w3svc!HTTP_REQ_BASE::OnFillClientReq+0x7a (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\httpio.cxx @ 253]

09 0129fec4 65f020d7 0129fedc 011a3568 0129ff20 w3svc!HTTP_REQUEST::DoWork+0x99 (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\httpreq.cxx @ 639]

0a 0129fee4 65f01b47 00000000 00000000 00000000 w3svc!CLIENT_CONN::DoWork+0x1aa (FPO: [Non-Fpo]) (CONV: thiscall) [D:\nt\private\inet\iis\svcs\w3\server\conn.cxx @ 781]

0b 0129ff08 65f01aa5 0129ff20 77e873b2 011a3568 w3svc!CreateClient+0x7b (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\inet\iis\svcs\w3\server\connect.cxx @ 310]

0c 0129ff4c 6d701443 011a3568 0000019b 00103880 w3svc!W3OnConnectEx+0x118 (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\inet\iis\svcs\w3\server\connect.cxx @ 215]

0d 0129ff80 6d702203 00000000 0000019b 011a356c ISATQ!AtqpProcessContext+0x23a (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\inet\iis\svcs\infocomm\atq\atqsupp.cxx @ 883]

0e 0129ffb4 77e887dd abcdef01 00000000 00012047 ISATQ!AtqPoolThread+0x1a8 (FPO: [EBP 0x0129ffec] [1,4,4]) (CONV: stdcall) [D:\nt\private\inet\iis\svcs\infocomm\atq\atqsupp.cxx @ 1127]

0f 0129ffec 00000000 6d7091f7 abcdef01 00000000 KERNEL32!BaseThreadStart+0x52 (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\windows\base\client\support.c @ 460]

 

 

As you can see above, badFil.dll encountered an unhandled exception while acting on the "PreProcHeader" notification, we know that because

of frame 04 (w3svc!HTTP_FILTER::NotifyPreProcHeaderFilters). It is helpful sometimes to exact information like what request

caused this filter to AV.

In this special case, using the debugger " kpn " command will show the exact request.

 

0:008> kpn

# ChildEBP RetAddr

00 0129f5bc 016b1da2 KERNEL32!RaiseException(unsigned long dwExceptionCode = 0x57, unsigned long dwExceptionFlags = 0, unsigned long nNumberOfArguments = 0, unsigned long * lpArguments = 0x00000000)+0x56 [D:\nt\private\windows\base\client\thread.c @ 1382]

01 0129f5dc 016b17c0 badfil!doRE1(int Variation = 1)+0x18 [H:\nT\PRIVATE\inet\iis\svcs\w3\gateways\filDBG\badfil.cpp @ 776]

02 0129fbf4 65f0354f badfil!HttpFilterProc(struct _HTTP_FILTER_CONTEXT * pfc = 0x00000001, unsigned long NotificationType = 0x4000, void * pvData = 0x08000002)+0x2be [H:\nT\PRIVATE\inet\iis\svcs\w3\gateways\filDBG\badfil.cpp @ 297]

03 0129fc1c 65f034bc w3svc!FILTER_LIST::NotifyFilters(class HTTP_FILTER * pFilter = 0x000003e8, unsigned long NotificationType = 0x4000, struct _HTTP_FILTER_CONTEXT * phfc = 0x00000002, void * NotificationData = 0x0129fc3c, int * pfFinished = 0x0129fedc, int fNotifyAll = 0)+0x9d [D:\nt\private\inet\iis\svcs\w3\server\httpfilt.cxx @ 968]

04 0129fc50 65f02cad w3svc!HTTP_FILTER::NotifyPreProcHeaderFilters(int * pfFinished = 0x0129fedc)+0x4c [.\filter.hxx @ 473]

05 0129fca8 65f02ac1 w3svc!HTTP_REQUEST::Parse(char * pchRequest = 0x006a9030 "GET /IISDebugLabs/Site/fil_re1.htm?sf=re1_v1 HTTP/1.1???", unsigned long cbData = 0x19b, unsigned long * pcbExtraData = 0x0129fcd4, int * pfHandled = 0x0129fce8, int * pfFinished = 0x0129fedc)+0x380 [D:\nt\private\inet\iis\svcs\w3\server\httpreq.cxx @ 1497]

06 0129fcec 65f029b5 w3svc!HTTP_REQ_BASE::OnCompleteRequest(char * pchRequest = 0x006a9030 "GET /IISDebugLabs/Site/fil_re1.htm?sf=re1_v1 HTTP/1.1???", unsigned long cbData = 0x19b, int * pfFinished = 0x0129fedc, int * pfContinueProcessingRequest = 0x0129feb8)+0x36 [D:\nt\private\inet\iis\svcs\w3\server\httpio.cxx @ 1289]

07 0129fd2c 65f028f8 w3svc!HTTP_REQ_BASE::UnWrapRequest(int * pfCompleteRequest = 0x0129fea4, int * pfFinished = 0x0129fedc, int * pfContinueProcessingRequest = 0x0129feb8)+0x1f4 [D:\nt\private\inet\iis\svcs\w3\server\httpio.cxx @ 634]

08 0129fd4c 65f027b3 w3svc!HTTP_REQ_BASE::OnFillClientReq(int * pfCompleteRequest = 0x0129fea4, int * pfFinished = 0x0129fedc, int * pfContinueProcessingRequest = 0x0129feb8)+0x7a [D:\nt\private\inet\iis\svcs\w3\server\httpio.cxx @ 253]

09 0129fec4 65f020d7 w3svc!HTTP_REQUEST::DoWork(int * pfFinished = 0x0129fedc)+0x99 [D:\nt\private\inet\iis\svcs\w3\server\httpreq.cxx @ 639]

0a 0129fee4 65f01b47 w3svc!CLIENT_CONN::DoWork(unsigned long BytesWritten = 0, unsigned long CompletionStatus = 0, int fIOCompletion = 0)+0x1aa [D:\nt\private\inet\iis\svcs\w3\server\conn.cxx @ 781]

0b 0129ff08 65f01aa5 w3svc!CreateClient(struct _CLIENT_CONN_PARAMS * ClientParam = 0x0129ff20)+0x7b [D:\nt\private\inet\iis\svcs\w3\server\connect.cxx @ 310]

0c 0129ff4c 6d701443 w3svc!W3OnConnectEx(void * patqContext = 0x011a3568, unsigned long cbWritten = 0x19b, unsigned long err = 0x103880, struct _OVERLAPPED * lpo = 0x00e83c20)+0x118 [D:\nt\private\inet\iis\svcs\w3\server\connect.cxx @ 215]

0d 0129ff80 6d702203 ISATQ!AtqpProcessContext(struct ATQ_CONTEXT * pAtqContext = 0x00000000, unsigned long cbWritten = 0x19b, struct _OVERLAPPED * lpo = 0x011a356c, int fRet = 1)+0x23a [D:\nt\private\inet\iis\svcs\infocomm\atq\atqsupp.cxx @ 883]

0e 0129ffb4 77e887dd ISATQ!AtqPoolThread(unsigned long * param = 0xece868ff)+0x1a8 [D:\nt\private\inet\iis\svcs\infocomm\atq\atqsupp.cxx @ 1127]

0f 0129ffec 00000000 KERNEL32!BaseThreadStart( * lpStartAddress = 0x6d7091f7, void * lpParameter = 0xabcdef01)+0x52 [D:\nt\private\windows\base\client\support.c @ 460]

 

 

 

 

Notice in frame 01 and 02 the line of the code as well as the name and location of the source code. Going back to the source code in badfil.cpp:

 

Line 297 looks like

 

DWORD WINAPI HttpFilterProc( HTTP_FILTER_CONTEXT *pfc, DWORD NotificationType, VOID *pvData )

{

.....

.....

else if (!strncmp(szS, "re1", 3))

{

return doRE1(Variation); //Line 297

}

.....

.....

}

 

Line 776 looks like

 

 

DWORD doRE1(int Variation)

{

DWORD dwThreadID;

HANDLE hThread;

if (1 == Variation)

{

RaiseException(ERROR_INVALID_PARAMETER, 0, 0, NULL); //line 776

}

if (2 == Variation)

{

hThread = CreateThread(NULL, 0, (LPTHREAD_START_ROUTINE)REContinuable, NULL, 0, &dwThreadID);

}

return 1;

}

1) Unknown Exception in a spawned thread: (Variation 2)

1- Debug Annotation

 

1) Without symbols

 

a) The faulting Stack

 

The stack backtrace of the thread that caused the Unhandled Exception would look like:

 

0:020> kvn50

# ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00 0198ffa0 016b1e0a 00000057 00000000 00000000 KERNEL32!RaiseException+0x37

01 0198ffec 00000000 016b1dfd 00000000 00000000 badfil!HttpFilterProc+0x908

 

 

In this stack backtrace, it is clear that the culprit is "badFil.dll". So it is enough to tell the customer to contact the dll vendor to fix it. If it is an in-house component and the customer would like help

from Microsoft, they should open an advisory case to troubleshoot the issue further.

 

b) The regiters values

 

0:020> r

eax=0198ff50 ebx=00000000 ecx=00000101 edx=ffffffff esi=00000000 edi=018fffdc

eip=77e9e8bb esp=0198ff48 ebp=0198ffa0 iopl=0 nv up ei pl zr na po nc

cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246

KERNEL32!RaiseException+37:

77e9e8bb e988c60100 jmp KERNEL32!GetThreadPriorityBoost+0x105 (77ebaf48)  

 

c) The disassmbly code

 

0:020> u eip

KERNEL32!RaiseException+37:

77e9e8bb e988c60100 jmp KERNEL32!GetThreadPriorityBoost+0x105 (77ebaf48)

77e9e8c0 8b4510 mov eax,[ebp+0x10]

77e9e8c3 83f80f cmp eax,0xf

77e9e8c6 0f8774c60100 jnbe KERNEL32!GetThreadPriorityBoost+0xfd (77ebaf40)

77e9e8cc 8945c0 mov [ebp-0x40],eax 77e9e8cf 8bc8 mov ecx,eax

77e9e8d1 48 dec eax

77e9e8d2 85c9 test ecx,ecx

 

2) With symbols including public symbols of "badFil.dll"

 

First, we need to add the public symbol path(company wide symbols) as well as symbols of our dll

a) Using the GUI:

- Click "File"

- Click "Symbol File Path"

- Type in SRV*C:\LabSymbols*http://msdl.microsoft.com/download/symbols;C:\IISDebugLabs\symbols\Pub and hit Enter

b) Using the ".sympath+" command:

0:008> .sympath+ SRV*C:\LabSymbols*http://msdl.microsoft.com/download/symbols

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

 

0:008> .sympath+ C :\IISDebugLabs\symbols\Pub (where public symbols of badFil.dll are located)

Symbol search path is:SRV*C:\LabSymbols*http://msdl.microsoft.com/download/symbols; C :\IISDebugLabs\symbols\Pub

 

Note: For more information on setting the symbol path for windbg, please refer to the debugger documentation for the .sympath command. This will describe

the "downstream store" feature that lets you download symbols to a symbol server of your own.

The stack backtrace of the thread that caused the Unhandled Exception would look like:

 

0:020> kvn50

# ChildEBP RetAddr Args to Child 00 0198ffa0 016b1e0a 00000057 00000000 00000000 KERNEL32!RaiseException+0x56 (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\windows\base\client\thread.c @ 1382]

01 0198ffec 00000000 016b1dfd 00000000 00000000 badfil!REContinuable+0xd

 

 

Now, with the public symbols lined up, we see that the function call that raised the exception is to "ReContinuable"

 

Again, In this call stack, it is clear that the culprit is "badFil.dll". So it is enough to tell the customer to contact the dll vendor to fix it. If it is an in-house component and the customer would like help

from Microsoft, they should open an advisory case to troubleshoot the issue further.

 

 

3) with Private Symbols "badExt.dll"

 

 

Point the debugger to use the private symbols

For company wide internal symbols, use \\symbols\symbols

For the component private symbols, use C:\IISDebugLabs\Symbols\Pri

 

Verify the component symbols are linet up.

 

0:008> lmv mbadfil

start end module name

015a0000 015a6000 badfil (pdb symbols) C:\IISDebugLabs\Symbols\Pri

Loaded symbol image file: badfil.dll

Image path: C:\IISDebugLabs\www\App\badfil.dll

Timestamp: Wed May 28 01:11:01 2003 (3ED444E5)

Checksum: 0000D9A0

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: badFIL.dll

OriginalFilename: badFIL.dll

ProductVersion: 5.00.0984

FileVersion: 5.00.0984

FileDescription: badFIL Filter DLL

LegalCopyright: Copyright (C) Microsoft Corp. 1981-1999

 

 

The stack backtrace of the thread that caused the Unhandled Exception would look like:

 

 

 

0:020> kvn

# ChildEBP RetAddr Args to Child

00 0198ffa0 016b1e0a 00000057 00000000 00000000 KERNEL32!RaiseException+0x56 (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\windows\base\client\thread.c @ 1382]

01 0198ffec 00000000 016b1dfd 00000000 00000000 badfil!REContinuable+0xd (CONV: stdcall) [H:\nT\PRIVATE\inet\iis\svcs\w3\gateways\filDBG\badfil.cpp @ 816]  

 

   

Notice in frame 00 and 01 the line of the code as well as the name and location of the source code. Going back to the source code in badFil.cpp:

 

Line 816 looks like

 

DWORD REContinuable()

{

RaiseException(ERROR_INVALID_PARAMETER, 0, 0, NULL); //line 816

return 1;

}

 


- Microsoft Confidential -