Collect Triofox Server Thread Info Using Windbg

When GCE is slow (for example, slow to browse web portal), we can use WinDbg to catch thread info on the GCE server side.

• Download and install WinDbg (https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk ); during the installation, select the 'Debugging Tools for Windows' checkbox only. 
• Find the corresponding 'SOS.dll' under 'C:\Windows\Microsoft.NET\Framework || Framework64 (based on your OS 32-bit || 64-bit)\ It should be under v4.0.30319 \SOS.dll'. 
• Copy 'SOS.dll' to the WinDbg installation folder, together with windbg.exe 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64 || x86(based on your OS 32-bit || 64-bit)'.
• Start WinDbg as Administrator.

• Contact Support (ticket@gladinet.com) with the Triofox version, to send you the Symbol files corresponding to the Triofox installed.
• unzip the Triofox symbol package. Should see list of folders like pdbsxxxx\namespace\bin
• Create a local folder C:\symbols, to store the symbol files downloaded from Microsoft (symbols from the Client can also be saved on this folder).
• From th WindDbg go to 'File' -> 'Symbol File Path', set symbol path to 'srv*C:\symbols*https://msdl.microsoft.com/download/symbols;path to unzipped symbol\namespace\bin' (for namespace. If working on other process like UploadDownloadProxy, change it to path to unzipped symbol\UploadDownloadProxy\bin)

• Press F6 to attach to the process. Find 'w3wp.exe' running as user 'namespace'.

• Type 'g' to continue. The command line field will show '*BUSY* Debuggee is running…'.

• Run the operation which causes GCE to be slow.
• When the system is slow, go to WinDbg and select 'Debug' -> 'Break', to break in.

• Type '.load SOS.dll', then '~*e!ClrStack' to collect thread info. Save the output in WinDbg.

• Click 'Debug' -> 'Detach Debuggee', to detach WinDbg.

• Send the saved output to Triofox support.