Pat,

In several of the logs that I have put up the message about debug
symbols not found has shown up. Is there a way to install additional
debug symbols to get a better stack?

Thanks

David L.

Nope. So long as IISState can get to microsoft.com, it will download the
symbols if they are available. Symbols are specific to the build of the
dll, so lining them up manually is not a trivial exercise (unless you are in
a lab).

Are the other symbols being located (e.g. for NTDLL)?

Pat
[quoted text, click to view]

Pat,

Ok so it is expected that the "symbols not found" show up sometimes.

In the log below Thread ID 4 and 23 those are to be expected?

If so that answers for microsoft debug info but what about some of these
others.

Thread ID 7 shows a problem with LEWebDBobj and that is one of my dlls
that was compiled to include debug symbols. There is another on Thread
ID 20 for file w3odbcci which is a third party dll.

If I seem to be nit picking things I am just trying to understand more
about how to read these logs myself.

Thanks

David L


Opened log file 'C:\iisstate\output\IISState-2364.log'

***********************
Starting new log output
IISState version 3.3.1

Mon Feb 21 14:19:58 2005

OS = Windows 2000
Executable: dllhost.exe
PID = 2364

Note: Thread times are formatted as HH:MM:SS.ms

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




Thread ID: 0
System Thread ID: 938
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0006fd28 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
01 0006fd50 7c57b3db KERNEL32!WaitForSingleObjectEx+0x71
02 0006fd60 77aab07e KERNEL32!WaitForSingleObject+0xf
03 0006fd80 77aaa88c
ole32!CSurrogateProcessActivator::WaitForSurrogateTimeout+0x4f
04 0006fd9c 01001230 ole32!CoRegisterSurrogateEx+0x169
05 0006ff24 010014c6 dllhost!WinMain+0xb0
06 0006ffc0 7c59893d dllhost!WinMainCRTStartup+0x156
07 0006fff0 00000000 KERNEL32!BaseProcessStart+0x3d




Thread ID: 1
System Thread ID: 948
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00b8ff30 77abc471 USER32!NtUserGetMessage+0xb
01 00b8ff70 77abc3bf ole32!CDllHost::STAWorkerLoop+0x40
02 00b8ff8c 77abc2fa ole32!CDllHost::WorkerThread+0xc2
03 00b8ff90 77ab5a5b ole32!DLLHostThreadEntry+0x9
04 00b8ffa8 77ab59b3 ole32!CRpcThread::WorkerLoop+0x22
05 00b8ffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
06 00b8ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 2
System Thread ID: 954
Kernel Time: 0:0:0.31
User Time: 0:0:0.31
Thread Type: Other
# ChildEBP RetAddr
00 00c9fc54 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
01 00c9fc80 6de8b9d0 KERNEL32!GetQueuedCompletionStatus+0x27
02 00c9fd94 6de8b908 TxfAux!WORK_QUEUE::WorkerLoop+0xa0
03 00c9ffb4 7c57b388 TxfAux!WORK_QUEUE::ThreadLoop+0x58
04 00c9ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 3
System Thread ID: 95c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 00ebff08 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
01 00ebff58 7c59a0c2 KERNEL32!WaitForMultipleObjectsEx+0xea
02 00ebff70 787f58ce KERNEL32!WaitForMultipleObjects+0x17
03 00ebffb4 7c57b388 COMSVCS!CEventDispatcher::PushEvents+0x4e
04 00ebffc0 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 4
System Thread ID: 960
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

Remote call is either to a MTA object or object not initialized. Also,
possible utility thread.
DCOM call being made to Process ID: 2184
Waiting on thread id: ffffffff

# ChildEBP RetAddr
00 00effb68 77d4256d ntdll!ZwRequestWaitReplyPort+0xb
01 00effb94 77d3ac56 RPCRT4!LRPC_CCALL::SendReceive+0x11e
02 00effba0 77b26c07 RPCRT4!I_RpcSendReceive+0x2c
03 00effbc0 77b26ad2 ole32!ThreadSendReceive+0xef
04 00effbd8 77b23ab6
ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x14f
05 00effc18 77b26946 ole32!CRpcChannelBuffer::SendReceive2+0x96
06 00effc28 77a6cc2a ole32!CRpcChannelBuffer::SendReceive+0x11
07 00effc88 77ab7e2f ole32!CAptRpcChnl::SendReceive+0xa9
08 00effce0 77d94c1a ole32!CCtxComChnl::SendReceive+0x124
09 00effcfc 77d9487d RPCRT4!NdrProxySendReceive+0x4c
0a 00efff44 77d95136 RPCRT4!NdrClientCall2+0x4f5
0b 00efff60 77d46e75 RPCRT4!ObjectStublessClient+0x76
0c 00efff70 787f5818 RPCRT4!ObjectStubless+0xf
0d 00efffb4 7c57b388
COMSVCS!CEventDispatcher::GetEventServerInfoThread+0x118
0e 00efffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 5
System Thread ID: 964
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 00f3fee0 7c59a243 ntdll!NtDelayExecution+0xb
01 00f3ff00 7c59a20e KERNEL32!SleepEx+0x32
02 00f3ff0c 787d12aa KERNEL32!Sleep+0xb
03 00f3ff7c 780085bc COMSVCS!PostData+0xf2
04 00f3ff88 77ab8107 MSVCRT!_endthreadex+0xc1
05 00000000 00000000 ole32!CCtxComChnl::FreeBuffer+0x3d




Thread ID: 6
System Thread ID: 968
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0126ff9c 77f842c4 ntdll!NtDelayExecution+0xb
01 0126ffb4 7c57b388 ntdll!RtlpTimerThread+0x42
02 0126ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 7
System Thread ID: 96c
Kernel Time: 0:0:55.875
User Time: 0:0:12.968
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for -
Thread Type: ASP
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

# ChildEBP RetAddr
00 012adc4c 779d91ef OLEAUT32!SysAllocStringLen+0x6a
01 012adc5c 1f4418d2 OLEAUT32!SysAllocString+0x1f
02 012adc68 1f446904 msado15!CSysString::operator=+0x27
03 012adc80 1f446859 msado15!CStdComObjectRoot::get_Name+0x1c
04 012adcc8 1f4468e4 msado15!CStdCollection::Append+0x68
05 012adcd4 1f4433b5 msado15!CConnection::AssociateRecordset+0x20
06 012adcf4 1f453ea4 msado15!CRecordset::SwapActiveConnection+0x7d
07 012add18 1f453222 msado15!CConnection::GetRecordset+0x82
08 012adde4 1f452da2 msado15!CQuery::Execute+0x802
09 012ade40 1f460f31 msado15!CCommand::_Execute+0x105
0a 012adeb4 1f45f530 msado15!CConnection::OpenRecordset+0xc5
0b 012adfec 01a8d0f5 msado15!CConnection::Execute+0x65f
WARNING: Stack unwind information not available. Following frames may be
wrong.
0c 012aeadc 6deb5c61 LEWebDBObj!DllCanUnloadNow+0x10967
0d 012aeafc 77aa3c65 TxfAux!CallFrame::Invoke+0x51
0e 012aeb50 77aa3f24 ole32!CCtxChnl::SyncInvoke2+0x84
0f 012aec00 77aa42db ole32!CCtxChnl::SendReceive2+0x1bb
10 012aed50 6de92727 ole32!CCtxChnl::OnCall+0x1fc
11 012aed68 6de94459 TxfAux!Interceptor::CallIndirect+0x107
12 012aed8c 11046071 TxfAux!InterceptorThunk+0x29
13 012aee60 779d7d5d LEWebUIObj!DllCanUnloadNow+0x2c3a3
14 012aee7c 6a9fa2fb OLEAUT32!DispCallFunc+0x15d
15 012af7d8 6a9fa0f4 MSVBVM60!EpiInvokeMethod+0x1e1
16 012af834 779e776d MSVBVM60!BASIC_CLASS_Invoke+0x52
17 012af86c 779b24ac OLEAUT32!IDispatch_Invoke_Stub+0x6d
18 012af8a4 77d9a3b7 OLEAUT32!IDispatch_RemoteInvoke_Thunk+0x3c
19 012afb60 77d93a2c RPCRT4!NdrStubCall2+0x604
1a 012afbc4 779e8f9f RPCRT4!CStdStubBuffer_Invoke+0xc8
1b 012afbe4 77b25616 OLEAUT32!CStubWrapper::Invoke+0x9f
1c 012afc28 77b258f1 ole32!SyncStubInvoke+0x61

For thread 4, yes. ASP.dll is not on the stack. IISState uses some
heuristics b/c symbols are not always available and sometimes you get a
false reading as a result of a guess. In this case, RPCRT4.dll is
associated w/DCOM calls and in IIS this means that this could be a ASP page.
It isn't, so ASP.dll is not there.

For thread 23, ditto.

Thread 7 shows your DLL making a MDAC call. The thread is actually
processing within MDAC at the time (i.e. your dll code was not actually
executing). This does not necessarily mean that the dll is having a problem
(or not) or that MDAC is/is not having a problem. To get IISState to pick
up the dll symbols, place the .pdb file on the server in the same directory
as the dll. For VB dlls, you will get .cls name and line numbers.

Thread 20. Correct. The dll in question has entered a WAIT state, pending
some event to be signaled.

No problem w/your questions. I love it when people ask. This is the only
way to become a better debugger.


pat



[quoted text, click to view]