1) Without symbols Finding the thread(s) causing High CPU using "!runaway" The !runaway debugger extension shows information about the time taken by each thread. Note that this command is used only in a live debug session, you cannot use it if you are analyzing a crash dump. Note: In this example, our CGI executable is running in only one thread (The second thread, is a dbg break thread), so basically when it goes to 100% CPU, that thread is the cause of that. But this how you generally find the thread(s) cause of the busy hang when the CGI is running with multiple threads. 0:001> !runaway User Mode Time Thread Time 4dc 0 days 0:00:05.658 f0 0 days 0:00:00.000 This shows that thread ID "4dc" took over 5 sec of CPU time, so that it the thread suspect. Thread ID "4dc" looks like: 0 Id: 80c.4dc Suspend: 1 Teb: 7ffde000 Unfrozen *** ERROR: Module load completed but symbols could not be loaded for badCGI.exe ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 00 0006ff70 01001daf 00000001 00444878 00442ce8 badCGI+0x184c 01 0006ffc0 77e9ca90 00000000 00341000 7ffdf000 badCGI+0x1daf 02 0006fff0 00000000 01001cb0 00000000 eeeeeeee KERNEL32!BaseProcessStart+0x3d Keep in mind that we are here debugging a custom CGI application that misbehaved. The web application relying on this CGI will eventually not run properly. So, in this stack backtrace, it is clear that the culprit is "badCgi.dll". So it is enough to tell the customer to contact the CGI 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 "badCgi.exe" 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 a nd hit Enter b) Using the ".sympath+" command: The stack backtrace of the thread that consumes high CPU looks like: 0 Id: 80c.4dc Suspend: 1 Teb: 7ffde000 Unfrozen ChildEBP RetAddr Args to Child 00 0006ff70 01001daf 00000001 00444878 00442ce8 badCGI!doCPU1+0x1d 01 0006ffc0 77e9ca90 00000000 00341000 7ffdf000 badCGI!mainCRTStartup+0xff (CONV: cdecl) [crtexe.c @ 338] 02 0006fff0 00000000 01001cb0 00000000 eeeeeeee KERNEL32!BaseProcessStart+0x3d (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\windows\base\client\support.c @ 504] Advanced Technique Disassembly code 0:000> u eip badCGI!doCPU1+1d 0100184c 3bc7 cmp eax,edi 0100184e 7706 ja badCGI!doCPU1+0x27 (01001856) 01001850 ffd6 call esi 01001852 2bc3 sub eax,ebx 01001854 ebf6 jmp badCGI!doCPU1+0x1d (0100184c) 01001856 6a01 push 0x1 01001858 58 pop eax 01001859 5f pop edi This looks like a loop in the extension code where we jump to 0100184cany time the value in eax is less than the value in edi (cmp eax,edi ). If the eax is greather than edi, we will be at 01001856 which is "pop ebx" 3) with Private Symbols "badCGI.exe" First, we need to add the private symbol path(company wide symbols) as well as private symbols of our exe a) Using the GUI: - Click "File" - Click "Symbol File Path" - Type in SRV*C:\LabSymbols*\\symbols\symbols;C:\IISDebugLabs\symbols\Pri a nd hit Enter b) Using the ".sympath+" command: .sympath+ SRV*C:\LabSymbols*\\symbols\symbols;C :\IISDebugLabs\symbols\Pri The stack backtrace of the thread that consumes high CPU looks like: 0 Id: 80c.4dc Suspend: 1 Teb: 7ffde000 Unfrozen ChildEBP RetAddr Args to Child 0006ff70 01001daf 00000001 00444878 00442ce8 badCGI!doCPU1+0x1f (CONV: stdcall) [C:\build\nT\PRIVATE\inet\iis\svcs\w3\gateways\cgiDBG\badcgi.cpp @ 330] 0006ffc0 77e9ca90 00000000 00341000 7ffdf000 badCGI!mainCRTStartup+0xff (CONV: cdecl) [crtexe.c @ 338] 0006fff0 00000000 01001cb0 00000000 eeeeeeee KERNEL32!BaseProcessStart+0x3d (FPO: [Non-Fpo]) (CONV: stdcall) [D:\nt\private\windows\base\client\support.c @ 504]
So from the dissasembly code, we noticed that this is a loop in the CGI code.
Lining up the source code (use ".srcpath+" debugger command to add the source path of the extension code), line 330 looks like:
DWORD doCPU1(int Variation)
{
if (1 == Variation)
{
DWORD dwStartTime = GetTickCount();
while( GetTickCount() - dwStartTime <= 30000 ) //Line 330
{
}
}
return 1;
}
Advanced Technique Remember that our web application is running in the IIS out of process pooled application (dllhost.exe). The CGI executable is loaded in its own memory space and it is basically spawned by "inetinfo.exe". So for all http requests involving directly the the CGI without passing via another extension will be processed by both inetinfo and the CGI executable without passing via dllhost. (for more information, please refer to the class docs Chapter:...). To get a feeling on how the CGI processing is made, let do the following: 1) In the command prompt, switch to the folder where the debugger is installed and run the following command: c:\ debuggers>windbg -pn inetinfo.exe 2) In WinDbg, let set a breakpoint in CreateProcess function of Kernel32 In the windbg command line, type in "bp KERNEL32!CreateProcessA" 3) In Windbg command line, type in "g" and hit "Enter" 4) Click the "AV CGI" button in this page. Notice that the debugger breaks, the command line is now available to run commands. The stack backtrace of the thread where the break point was hit looks like: 0:010> kp ChildEBP RetAddr 0136ee98 65f1be75 KERNEL32!CreateProcessA(char* lpApplicationName = 00000000 "", char* lpCommandLine = 0136f4b0 ""C:\IISDebugLabs\www\App\badCgi.exe" ", _SECURITY_ATTRIBUTES* lpProcessAttributes = 00000000 , _SECURITY_ATTRIBUTES* lpThreadAttributes = 00000000 , int bInheritHandles = 1, unsigned long dwCreationFlags = 0xc, void* lpEnvironment = 0136eed4 , char* lpCurrentDirectory = 0136fba8 "C:\IISDebugLabs\www", _STARTUPINFOA* lpStartupInfo = 0136f5b4 , _PROCESS_INFORMATION* lpProcessInformation = 0136f658 ) [D:\nt\private\windows\base\client\process.c @ 715] 0136f678 65f1b925 w3svc!HTTP_REQUEST::ProcessCGI(EXEC_DESCRIPTOR* pExec = 00e9eb2c , STR* pstrPath = 00000000 , STR* pstrWorkingDir = 0136fd10 , int* pfHandled = 0136feb0 , int* pfFinished = 0136fedc , STR* pstrCmdLine = 0136f5fc )+0x4c3 [D:\nt\private\inet\iis\svcs\w3\server\cgi.cxx @ 1179] 0136fd48 65f2a610 w3svc!HTTP_REQUEST::ProcessGateway(EXEC_DESCRIPTOR* pExec = 00e9eb2c , int* pfHandled = 0136feb0 , int* pfFinished = 0136fedc , int fTrusted = 0)+0x34e [D:\nt\private\inet\iis\svcs\w3\server\cgi.cxx @ 919] 0136fec4 65f020d7 w3svc!HTTP_REQUEST::DoWork(int* pfFinished = 0136fedc )+0x43f [D:\nt\private\inet\iis\svcs\w3\server\httpreq.cxx @ 839] 0136fee4 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] 0136ff08 65f01aa5 w3svc!CreateClient(_CLIENT_CONN_PARAMS* ClientParam = 0136ff20 )+0x7b [D:\nt\private\inet\iis\svcs\w3\server\connect.cxx @ 310] 0136ff4c 6d701443 w3svc!W3OnConnectEx(void* patqContext = 012742d8 , unsigned long cbWritten = 0xe4, unsigned long err = 0x1131e8, _OVERLAPPED* lpo = 00e897b8 )+0x118 [D:\nt\private\inet\iis\svcs\w3\server\connect.cxx @ 215] 0136ff80 6d702203 ISATQ!AtqpProcessContext(ATQ_CONTEXT* pAtqContext = 00000000 , unsigned long cbWritten = 0xe4, _OVERLAPPED* lpo = 012742dc , int fRet = 1)+0x23a [D:\nt\private\inet\iis\svcs\infocomm\atq\atqsupp.cxx @ 883] 0136ffb4 77e887dd ISATQ!AtqPoolThread(unsigned long* param = abcdef01 )+0x1a8 [D:\nt\private\inet\iis\svcs\infocomm\atq\atqsupp.cxx @ 1127] 0136ffec 00000000 KERNEL32!BaseThreadStart(* lpStartAddress = 6d7091f7 , void* lpParameter = abcdef01 )+0x52 [D:\nt\private\windows\base\client\support.c @ 460] Note that the second parameter to CreateProcess is the command line to trun that process which is in this case "C:\IISDebugLabs\www\App\badCgi.exe" Let try to get the whole HTTP request that w3svc received. For this, let dump the EXEC_DESCRIPTOR class. 0:010> dt EXEC_DESCRIPTOR 00e9eb2c +0x000 _pstrURL : 0x00e9e370 +0x004 _pstrPhysicalPath : 0x00e9e5e0 +0x008 _pstrUnmappedPhysicalPath : 0x00e9e610 +0x00c _pstrGatewayImage : 0x00e9eac0 +0x010 _pstrPathInfo : 0x00e9e400 +0x014 _pstrURLParams : 0x00e9e3d0 +0x018 _pdwScriptMapFlags : 0x00e9eabc -> 0 +0x01c _pGatewayType : 0x00e9e060 300002 ( GATEWAY_CGI ) +0x020 _pRequest : 0x00e9e008 +0x024 _hChildEvent : (null) +0x028 _fMustWaitForChildEvent : 0 +0x02c _pParentWamRequest : (null) +0x030 _dwExecFlags : 0 +0x034 _pMetaData : 0x00e9ecd8 +0x038 _pPathInfoMetaData : (null) +0x03c _pPathInfoURIBlob : (null) +0x040 _pAppPathURIBlob : (null) Now let dump the HTTP_REQUEST class. 0:010> dt HTTP_REQUEST 0x00e9e008 +0x000 __VFN_table : 0x65f08680 +0x008 _cFilesSent : 0 +0x00c _cFilesReceived : 0 ...... ...... +0x9a8 _bufClientRequest : BUFFER ...... ...... +0xbac _pFileNameLock : (null) +0xbb0 _fPossibleDefaultExecute : 0y0 =65f465b0 HTTP_REQUEST::sm_GetInfoFuncs : [26] 0x65f26a87 w3svc!HTTP_REQUEST::GetInfoA+0 +0xbb4 _strDLCString : STR The "_bufClientRequest " points to the buffer where the HTTP request is stored. 0:010> da poi(0x00e9e008 + 0x9a8 ) 006ae398 "GET /IISDebugLabs/App/badCgi.exe" 006ae3b8 "?s=cpu1_v1 HTTP/1.1..Accept: */*." 006ae3d8 ".Accept-Language: en-us..Accept-" 006ae3f8 "Encoding: gzip, deflate..User-Ag" 006ae418 "ent: Mozilla/4.0 (compatible; MS" 006ae438 "IE 6.0; Windows NT 5.0)..Host: l" 006ae458 "ocalhost..Connection: Keep-Alive" 006ae478 "...." 5) In the windbg command line, type in "g" and hit "Enter" Notice a second windbg window is displayed, this is the one attached to the CGI executable "badCgi.exe". 6) In the Windbg instance attached to "badCgi.exe" type in "q" and hit "Enter". 7) Finaly, back to the main WinDbg window, press "Ctrl-Break" to break in to the debugger, type in "q" and hit "Enter"
|